Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×

Comment Re:Time for vector processing again (Score 2, Insightful) 251

Faster computation doesn't help communication-limited tasks. Faster communication doesn't help computation-limited tasks.

Computation is communication. It's communication between the CPU and memory.

The problem with multicore is that, as you add more cores, the increased bus contention causes the cores to stall making so they cannot compute. This is why many real supercomputers have memory local to each CPU. Cache memory can help, but just adding more cache per core yields diminishing returns. SMP will only get you so far in the supercomputer world. You have to go NUMA for performance, which means custom code and algorithms.

Programming

Submission + - Components, Builds and Configuration Management

command.com writes: I've recently been placed in charge of configuration management for a modest programming team in a Fortune 500. As a software engineer, I've used version control software before, but I've never had to do it for 100 projects. The repository contains multiple products managed by different development teams on independent release schedules, and some products used shared components (DLLs). The current repository is a mess — you basically have to check out everything in order to build some products because there's no telling what dependencies it's pulled in — and it needs to get reorganized to allow us to achieve CMMI compliance. Best practices on managing repositories of this size and complexity are hard to come by, so I'm looking for some some real world experience on how other people have tackled this problem. How did you organize project folders (e.g. src, bin, include directories per project)? How was the nightly build affected by shared components? How did you track and manage dependencies? If you had to make deployment packages (MSI), how did you manage the shared components?

Bad Password Allowed Swedish Watergate 248

fredr1k writes "The Swedish Watergate reported earlier this week was possible because of the usage of terrible weak passwords (Swedish) and a not functional IT policy. The Swedish newspaper Göterborgs-Posten reports the source of the password was a partymember who's account was "sigge" with password "sigge" and was "stolen" in march this year. Seasoned Slashdot readers would call it "a-not-so-hard-to-crack-password". "

Slashdot Top Deals

Two can Live as Cheaply as One for Half as Long. -- Howard Kandel

Working...