Follow Slashdot stories on Twitter


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).


Comment: Re:TIOBE methodology is so flawed it's pointless (Score 1) 535

by tietokone-olmi (#31762490) Attached to: C Programming Language Back At Number 1

Dude, it's a long-term study. It doesn't matter if their metric isn't the absolute bestest metric you could come up with to measure impact etc. right now. What matters is that their metric works over several decades and that the results remain comparable between then and now.

tl;dr -- you want to look at the graphs, not the numbers.

Comment: Re:TFS is a bit light on details (Score 2, Interesting) 181

by tietokone-olmi (#29267953) Attached to: AMD Packs Six-Core Opteron Inside 40 Watts

Except that with multiprocess concurrency (i.e. non-multithreaded Apache on Unix), you actually gain in a NUMA setup like the Opterons have been from day 1. See, in the optimum case in a NUMA environment, the server process that handles a request gets an entire memory bus for itself. That's far more scalability than with multithreading in the absence of memory duplication, which AFAIR Linux doesn't implement on a per-thread basis in the same address space.

This is why Opterons practically own the 4-socket x86 space: unlike with Intel's older "hub-style" busses, on a NUMA system aggregate memory bandwidth goes up as sockets are added because the number of memory busses increases also.

The price one pays for pursuing any profession, or calling, is an intimate knowledge of its ugly side. -- James Baldwin