Become a fan of Slashdot on Facebook


Forgot your password?
Slashdot Deals: Deal of the Day - Pay What You Want for the Learn to Code Bundle, includes AngularJS, Python, HTML5, Ruby, and more. ×

Journal FortKnox's Journal: /. Slow as Dirt 5

Man, slashdot is running like tar today!

I'd really like to know where the bottleneck is. Is it too many hits to the database, or something that J2EE technology would save (connection pooling, db caching, etc...)?

Has VA sold off some of the power-servers or bandwidth that once existed for OSDN??

Inquiring minds want to know!
This discussion has been archived. No new comments can be posted.

/. Slow as Dirt

Comments Filter:
  • ... that this guy writes (well, it's good, but beware the links), but go to RealWorldStuff's journal [] for a possible explanation.
  • I can say with certainty that a Java setup of any kind would not be an improvement over their current setup. The Slashdot bottleck is most likely not the rendering software (mod_perl I think in their case) but the database.

    Going to shared memory may provide performance improvements, but it involves a lot more custom coding, and can end up being brittle. Outside of that, you can go for RAID, clustering, or other partitioning solutions, or simply beef up to faster boxes with a shitload of RAM (like, over 2GB minimum).

    On the outside, PHP with Zend or PHP Accelerator may be a slightly faster model than mod_perl.

One picture is worth 128K words.