Collecting feature requests

Luke Schierer lschiere at pidgin.im
Mon Jan 5 19:55:53 EST 2009


On Mon, Jan 05, 2009 at 03:14:55PM -0400, Craig Harding wrote:
> Isn't the trac-hack vote (http://www.trac-hacks.org/wiki/VotePlugin)
> plugin what we all need - a voting system?
> 
> This plugin keeps it all under the same roof. Why buy a truck and car
> when winter tires on the car is sufficient.
> 
> Is it possible to have the vote number as a column in the search results?
> 
> Craig.

That is precisely what we installed before turning off the brainstorm
instance.  Further work is, naturally, needed to fully replicate
brainstorm's capabilities.  I think Kevin hopes to find time to try to
do at least some of that work, but I equally suspect that he wouldn't
mind a patch to the plugin.

Luke

> 
> On 1/5/09, Felipe Contreras <felipe.contreras at gmail.com> wrote:
> > On Mon, Jan 5, 2009 at 8:45 PM, Kevin Stange <kevin at simguy.net> wrote:
> >  > Felipe Contreras wrote:
> >  >> On Sun, Jan 4, 2009 at 2:33 AM, Luke Schierer <lschiere at pidgin.im> wrote:
> >  >>> On Sat, Jan 03, 2009 at 03:32:53PM -0800, Casey Ho wrote:
> >  >>>> Drupal's performance is a straw man argument.  I had configured Drupal
> >  >>>> to automatically shut down in the case of high load/high usage- based
> >  >>>> on what you had said earlier.  Drupal was not responsible for the
> >  >>>> server downtine earlier this week.
> >  >>> I am not and have not blamed drupal for the downtime earlier this week.
> >  >>> I'm just asserting, based on my experience, that is a huge resource hog,
> >  >>> resources that we often find scarce.
> >  >>>
> >  >>> That it will, supposedly, shut itself down in such at such a time, but I
> >  >>> think we are better served with a mechanism that we can have up all the
> >  >>> time.
> >  >>
> >  >> This is what the Brainstorm author commented[1] about this:
> >  >>
> >  >> Concerning Drupal and Brainstorm performance, I'd like to share my
> >  >> experience. I'm its author and I'm part of the team managing
> >  >> brainstorm.ubuntu.com.
> >  >>
> >  >> During the launch of Ubuntu Brainstorm, we faced some performance
> >  >> issues, for two days. Why? Because 1/ we didn't activated Drupal
> >  >> caching and 2/ the launch of Brainstorm was *highly* popular (300,000
> >  >> votes the first day, slashdotted, digged, wired).
> >  >> But after that, we set up the Drupal caching, then a Squid proxy
> >  >> (better than drupal caching), and things calmed down.
> >  >> We are now running well on a shared Xen host with a dozen of others
> >  >> virtual machines, at 3,000 votes a day, and dozens of thousands of
> >  >> unique visits/day.
> >  >
> >  > For what it's worth, Xen provides guaranteed fixed resource allocation.
> >  >  We are on an OpenVZ virtual machine which provides shared resource
> >  > allocation, and we have no idea how many other machines are on our
> >  > system with us.
> >
> >  Ok, but he is providing an idea to avoid the issues you where mentioning before.
> >
> >  So at least there's a possibility that there won't be load issues, right?
> >
> >
> >  --
> >  Felipe Contreras
> >
> >  _______________________________________________
> >  Devel mailing list
> >  Devel at pidgin.im
> >  http://pidgin.im/cgi-bin/mailman/listinfo/devel
> >
> 
> _______________________________________________
> Devel mailing list
> Devel at pidgin.im
> http://pidgin.im/cgi-bin/mailman/listinfo/devel
> 




More information about the Devel mailing list