Hi,
I've noticed something but don't know how to test for it other than what I experience.
I am running eSignal ver 10.4.1574.925 on an Intel I7 965 cpu, 6 GiG RAM & Win XP Pro (waiting for Window 7) (I know 32 bit OS & software only uses a max of 3 GIGs of RAM).
The I7 CPU monitor avg usage is 13% with the primary core averaging ~ 80%.
With this configuration I can open the "File" menu, "Edit Studies", etc. with little lag. However, once I open an efs file via the MS Explorer by selecting the efs from within a directory in Explorer, eSignal seems to get burdened with a permanent overhead that now causes significant lag (over 30 seconds to minutes) when accessing "File" menu, "Edit Studies", etc. and the primary CPU core now pegs at over 95% constantly. This continues even after I close the efs editor.
I have to close and reload eSignal before this overhead is cleared and the lag dissappears.
Note: even while the lag exists (before closing and reloading eSignal) I can open other programs like MS Word, Excel, Internet Explorer and they run fine with no lag but eSignal must be closed and reloaded before the overhead that causes the lag dissapears.
I hope this helps.
Wayne
I've noticed something but don't know how to test for it other than what I experience.
I am running eSignal ver 10.4.1574.925 on an Intel I7 965 cpu, 6 GiG RAM & Win XP Pro (waiting for Window 7) (I know 32 bit OS & software only uses a max of 3 GIGs of RAM).
The I7 CPU monitor avg usage is 13% with the primary core averaging ~ 80%.
With this configuration I can open the "File" menu, "Edit Studies", etc. with little lag. However, once I open an efs file via the MS Explorer by selecting the efs from within a directory in Explorer, eSignal seems to get burdened with a permanent overhead that now causes significant lag (over 30 seconds to minutes) when accessing "File" menu, "Edit Studies", etc. and the primary CPU core now pegs at over 95% constantly. This continues even after I close the efs editor.
I have to close and reload eSignal before this overhead is cleared and the lag dissappears.
Note: even while the lag exists (before closing and reloading eSignal) I can open other programs like MS Word, Excel, Internet Explorer and they run fine with no lag but eSignal must be closed and reloaded before the overhead that causes the lag dissapears.
I hope this helps.
Wayne
Comment