Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror

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: PatchSee FTW (Score 1) 374

by TobiasS (#37437532) Attached to: Ask Slashdot: Clever Cable Management?
Aside from obviously keeping your cable management channels neat, PatchSee cables have been great. No more tracing a cable from the patch panel to the switch ... just inject light on one end and clearly see where the other end terminates. http://www.patchsee.com/ They are a bit more expensive than regular patch cables but totally worth it

Comment: sure in general more hardware is cheaper (Score 1) 465

by TobiasS (#26185707) Attached to: Hardware Is Cheap, Programmers Are Expensive

However, I have seen plenty of example where that is not true.

Enterprise databases are a great example. While the DBA can often do alot to compensate for dev's bad db code ... sometimes that just is not enough.
A fulltime employee can work on optimizing code for an entire year before it pays to add another node to the cluster. (server hardware, hba's, fiber switch ports and most importantly oracle licenses). Interestingly enough PHB's often times choose expanding the infrastructure eventhough the ROI is not there citing opportunity cost, etc.

Another favorite are processes running on new hardware ... the dev just simply did not consider parallelizing the tasks and opted for a monolithic single process approach.

From my experience most of these issues dont go away by horizontally scaling and eventually they come back to haunt you one way or another.

Surprisingly, the added cost of administrating added infrastructure is never part of the calculation ... the only consideration is the cost of hardware.

Comment: Re:Not completely fair (Score 1) 258

by TobiasS (#26176221) Attached to: Java Performance On Ubuntu Vs. Windows Vista

all jvms except for the 32 bit win32 version default to -server for this type of hardware.
server class hardware for the jvm is defined as min. 2 cpu's and 2GB memory both of which are present in the test machine.

I saw no mention in the article whether the vista install was 32 or 64 bit.

If it was running with default vm options it could make quite a difference on vista.

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (7) Well, it's an excellent idea, but it would make the compilers too hard to write.

Working...