Page is a not externally linkable
- Code, Content, and Presentation
-- Content Management
---- Digg Clone : Pligg Vs. Drupaligg Vs. Drigg


ergophobe - 7:45 pm on Jul 10, 2008 (gmt 0)


It was months ago, so no worries now.

As for the rest. Check. Got it. Understood. "All you are saying, is give Drigg a chance."

Since both are free and open source, I can only suggest that anyone interested Pligg, Drigg or what have you, install both, run Apache Bench or some more specific script designed to stress test (i.e. to do inserts as well as just request pages) and see which meets your needs.

Short of that, it's all hearsay.

[rant]

Perhaps more to the point, though, I see people all the time who have never built a high-volume site (for example, ME), who obsess about scalability, certain that their idea is so hot that the data center is going to have to put in additional air conditioners to cool the place down with the load their site will be creating. If Brett or Dries or Matt [choose last name] is starting a new site and he thinks it's going to go big, then I would say that scalability is a serious consideration. Usually, it's not (think of all the people who worry about forum software scalability and then have 500 threads after two years).

Since my sites churn along at 10K visits per month or less (usually anyway), I just don't worry about scalability (oh! shame on me!?). If something starts getting 10K visits per day, I'll rewrite and scale then, but it hasn't happened for me and doesn't happen for most people with killer ideas for the latest forum/tagging/digg-clone/etc site.

I know of people who have had site ideas for several years who never launch because they can't find a scalable solution and, as it turns out, you don't need any software at all to handle zero hits per day.

All things being equal, I would rather have the most efficient solution, but all things are rarely equal. So personally, assuming that it's going to be one of MY sites (i.e. a few thousand visitors per month), I would go with whichever one is easiest to administer and has the feature I want, provided it passes a basic stress test.

Recipe for actually getting a site built: prototype, launch refine.

Recipe for having the best idea that never leaves your hard drive: prototype, refine, launch.
[/rant]

And FWIW, the latest test results I've seen comparing Joomla, Drupal and Typo3, show Drupal performs the best if all of them have caching on. Still, it ain't fast and light and never will be compared to something designed to do only one thing. So many DB queries and includes to produce one simple page. Cache cache cache. But it still has its limits, but since The Onion runs on it, I don't see myself ever reaching those limits. Maybe I don't dream big enough, but the things that interest me are generally too obscure... I'm a jack of all things long tail if there ever was one!


Thread source:: http://www.webmasterworld.com/content_management/3553652.htm
Brought to you by WebmasterWorld: http://www.webmasterworld.com