Re: Why is Trac so sluggish?

The system you see in place today bears very little resemblance to  
what we've ordered and are committing to put in place going forward.   
There are a lot of services currently doubled (and tripled) up on the  
same machines and the machines themselves are nothing to write home  
about.  It was never our intention to use this equipment long term and  
the "right" configuration is many times better than what we're using  
now.  Please be patient - we're working to get the new systems in  
place as fast as we can.

- Jordan

On Aug 31, 2006, at 10:03 PM, Mark Duling wrote:

> Charlie Allom <[email protected]> writes:
>> Yes, macosforge has new hardware "on order" - hold tight, and soon  
>> trac
>> will speed up.
>>
> I hope the hardware will make it at least 20 times faster than it  
> has been
> today because it is a actually quite an understatement to call it  
> sluggish.
>>
>>> Also, is there a way to get a number count on the number of bugs  
>>> like
>>> bugzilla used to do by default?
>>
>> active tickets? http://svn.macosforge.org/projects/macports/report/1
>>
> Unless I've overlooked it I don't see a number count of the bugs on  
> that
> report or the others I saw.
>>
>>> I see subversion does not add a timestamp and committer to the
>>> portfile.  Are we supposed to remove the old cvs info when  
>>> committing
>>> to subversion?
>>
>> i think this is being discussed in the thread "SVN keywords
>> substitution" ?
>
> I see, I didn't fully understand what that was about.
>
> Mark
>
> _______________________________________________
> Darwinports mailing list
> [email protected]
> http://www.opendarwin.org/mailman/listinfo/darwinports