John Aquilio

Thanks Holger Vogt. I observed that passing "save none" reduces the memory growth (as indicated in task manager) over a 5 minute period from 300MB to 210MB, a saving of about 90MB for 5 minutes of simulation for this circuit. I am yet to try out the XSPICE improvements.

Thanks Holger Vogt. I observed that passing the "save none" reduces the memory growth (as indicated in task manager) over a 5 minute period from 300MB to 210MB, a saving of about 90MB for 5 minutes of simulation for this circuit. I am yet to try out the XSPICE improvements.

Yes, I use 'bg_run' to run spice in background thread. I just updated my post above with some additional findings. Basically, I noticed that when the control section is added, the callback function got called in caller's thread instead of happening in background thread. Below is the relevant callstack. As can be seen here, the call to ngSpice_Circ (last but one line in callstack) resulted in callback happening in the same thread instead of background thread, contrary to what is stated in section...

Yes, I use 'bg_run' to run spice in background thread. I just updated my post above with some additional findings. Basically, I noticed that when the control section is added, the callback function got called in caller's thread instead of happening in background thread. Below is the relevant callstack. As can be seen here, the call to ngSpice_Circ (last but one line in callstack) resulted in callback happening in the same thread instead of background thread, contrary to what is stated in section...

Yes, I use 'bg_run' to run spice in background thread. I just updated my post above with some additional findings. Basically, I noticed that when the control section is added, the callback function got called in caller's thread instead of happening in background thread. Below is the relevant callstack. As can be seen here, the call to ngSpice_Circ (last but one line in callstack) resulted in callback happening in the same thread instead of background thread, contrary to what is stated in section...

Yes, I use 'bg_run' to run spice in background thread. I just updated my post above with some additional findings. Basically, I noticed that when the control section is added, the callback function got called in caller's thread instead of happening in background thread. Below is the relevant callstack. As can be seen here, the call to ngSpice_Circ (last but one line in callstack) resulted in callback happening in the same thread instead of background thread, contrary to what is stated in section...

Yes, I use 'bg_run' to run spice in background thread. I just updated my post above with some additional findings. Basically, I noticed that when the control section is added, the callback function got called in caller's thread instead of happening in background thread. Below is the relevant callstack. As can be seen here, the call to ngSpice_Circ (last but one line in callstack) resulted in callback happening in the same thread instead of background thread, contrary to what is stated in section...

Yes, I use 'bg_run' to run spice in background thread. I just updated my post above with some additional findings. Basically, I noticed that when the control section is added, the callback function got called in caller's thread instead of happening in background thread. Below is the relevant callstack. As can be seen here, the call to ngSpice_Circ (last but one line in callstack) resulted in callback happening in the same thread. MyApp.exe!Ckt::cCktSim::StaticSpiceData(vecvaluesall * pVecData, int...