Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • To your list of "how do virtual computers behave" I would love to see how it handles something like qemu, or something else which would normally really thrash the cache.

    I'm already seeing recommendations that the dual core intels aren't usable for two qemu sessions because of that issue, I would expect the "32 processors" to show even more pronounced cache thrashing problems.

  • You can find more numbers on Colm MacCárthaigh’s weblog [stdlib.net]. In particular, don’t miss the Niagara vs ftp.heanet.ie Showdown [stdlib.net].

  • One that I’m interested is comparing the performance of a big 16 CPU Itanium box against the T2000’s 8 CPUs that behave like 32 CPUs.

    note that the niagara chip (the one in the t2000) is not powerful in number crunching and other high-cpu loads such as... compilations. it's good for multi-threading and parallel tasks, such as java application servers and this kind of stuff. so i can foresee that your 16-ways itanium box will outperform the t2000 with a high margin. but for web servers and othe

    • We use the t2000 mentioned in the blog above as a terminal server. I guess running shells for 100+ users is about as parallel as you get.