I know I have missed out on the list for a good long time, but, I thought I recalled that usb read/writes were the worst thing one could try to do while using EMC2. I realize that it was done as stress testing. I just thought those read/writes were pretty much suggested to be avoided as they absolutely killed a systems performance. Please, re-educate me if I am wrong.
Kyle On Tue, Feb 8, 2011 at 10:51 AM, Kent A. Reed <knbr...@erols.com> wrote: > I simultaneously ran several copies of glxgears, firefox, vlc movie > player, and took directory listings from attached usb hard drives. > > The relevant test numbers are: > > 1ms thread: max interval 1009084 / max jitter 12603 > 25us thread: max interval 29248 / max jitter 14321 > Regards, > Kent > > > PS - I'll post these numbers to the wiki in a while. ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
