On Fri, Jun 5, 2009 at 9:05 PM, Lance Hendrix <la...@lancehendrix.com> wrote:
> If we can't find something else then wget

http://twill.idyll.org/testing.html

> characteristics like simulated number of users, etc).  But then again,
> perhaps we could have something basic for people to do a simple baseline
> of their installation with wget and some scripting and a more detailed
> testing configuration for others.  Let me know if you have any ideas,
> objections, suggestions, criticism, or general gripes... ;-)

Seems like you catched all major flaws in this performance benchmark
pretty well.

Performance test needs real DB with big data table. When people switch
from old Trac version to a new one and notice serious performance
decrease they usually already have about 1000 tickets inside.

This leads to conclusion that read-only tests are better be executed
by final users on their production DB (in a safe testing environment
with all external output - email etc. turned off) with profiling
turned on to gather statistics on lockups and catch other surprises
that can only occur when several processes are executed concurrently.

> Also, I don't recall or haven't yet found any information regarding
> recommended configurations (may be a can of worms you don't want opened)
> or at least some information regarding the various trade offs of the
> various configuration options (tracd vs. mod_python vs. wsgi and mysql
> vs. sqlite vs. postgres).  I do seem to recall some information in the
> various administration/install documentation, but I don't know if it
> would be valuable to have something that is more focused on this topic?
>
It would be nice to have at least 2D table/matrix with
supported/tested configurations of Trac/OS/DB vs Server/CGI/FastCGI
for an overview and quick links to platform/server installation
instructions.

It may also contain bug count related to specific OS/Trac version and
colored status of latest test results. AFAIR Debian has a page like
this for its package builders and dedicated page for bugs related to
Trac at http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=trac;dist=unstable
 It seems that Debian lost all Trac maintainers, but that's another
story.

WBR,
-- 
anatoly t.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to trac-dev@googlegroups.com
To unsubscribe from this group, send email to 
trac-dev+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to