On 04/09/10 02:35, Henrik Johansen wrote: > I have spend some time profiling the bacula-sd under production load on > Solaris. Besides checking for signs of lock contention and memory / CPU > usage issues I also tracked the I/O statistics for each file descriptor > opened within the bacula-sd process while running. > > According to my notes there was a noticeable change in throughput when > testing 100 concurrent jobs against 100 separate devices (100 separate > volumes) compared against writing the same jobs against 20 concurrent > volumes. > > I/O throughput increased with more concurrency.
That is an extremely interesting, and somewhat counter-intuitive, result. > There also was a noticeable increase in CPU time between those tests > (more concurrency == more CPU time spend by the bacua-sd process) but > nothing that worried me (but may need further investigation to fully > understand). > > The above is specific to our setup so YMMV on other platforms and hardware. What precisely is the hardware platform for this test? -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 [email protected] [email protected] [email protected] Renaissance Man, Unix ronin, Perl hacker, Free Stater It's not the years, it's the mileage. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
