Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?

Comment Re:DreamHost (Score 1) 456

I love DreamHost. I've been using them for several years. When they had a rough period a few years ago I switched to MediaTemple's gridserver (although I kept my DH account open and continued to host some less active sites there). Recently I became dissatisfied with MediaTemple when it started getting really slow and I was constantly getting GPU overages for two moderately busy self-hosted WordPress sites. I finally switched back to DreamHost and I'm very happy with them.

I use a DreamHost VPS, which lets me change the memory allocation as needed and reboot the server at any time. I recently switched my VPS from Apache to Nginx, which gave me a dramatic performance increase and reduction of memory usage.

Comment Re:More speed ... thttpd (Score 1) 304

I switched my virtual private server from Apache to Nginx and I found the memory usage dropped by nearly half and it runs a lot faster. I have two wordpress sites and one Drupal site on that server. The default Apache configuration uses a separate process for each connection, so the memory usage balloons with a lot of activity. Nginx defaults to use a single process, and the memory usage remains constant no matter how busy it gets.

Submission + - SPAM: Drupal Creator Dries Buytaert on Drupal 7

itwbennett writes: The Drupal community has been working on Drupal 7 for two years, and there are 'hundreds of changes' to show for it, says Drupal creator Dries Buytaert in an interview with ITworld's Esther Schindler on the occasion of Drupal 7 going into Alpha test this week. Most notable for end users are 'some massive usability improvements,' says Buyteaert, while site builders will see the greatest changes in the Drupal Content Construction Kit (CCK), which has been moved into the Drupal core. But one thing that hasn't changed is the not-so-easy upgrade path. 'The upgrade path for a Drupal site has never been really easy, to be honest,' Buytaert says. 'We do break backwards compatibility. It's a little bit painful because it requires all of the contributed modules — and there's 4,000-5,000 of them — to make changes.' But Buytaert doesn't think that's all bad. 'Innovation is key. Backwards compatibility limits innovation,' Bytaert contends. 'The rule we have is: We'll break the API if it makes a better API, and if it allows good innovation and progress to be made. Also: The second rule is that we'll never break people's data. We'll always provide an upgrade path for the data.'
Link to Original Source

Slashdot Top Deals

Don't hit the keys so hard, it hurts.