On Thu, Apr 02, 2009 at 04:58:34PM +0300, Agnislav Onufrijchuk wrote: > Kenneth Marshall wrote: > > Are these 4000 tickets per day or 4000 updates total? 100000 tickets > > is not very many if you actually generate 4000 tickets per day. Do > > you "shred" old tickets to remove them from your DB? > > > 4000 Transactions, not tickets per day. > Good, that means every alternative will meet your needs performance-wise.
> >> - File system: Ext3/XFS/JFS/...? > > Use the supported/recommended one for your chosen OS. > > > Even if I'll choose FreeBSD, I will not use UFS :) It's too slow. Makes sense. > > >> - apache 2.2 or nginx? > > Apache all the way. > > > What advantages does it have? The biggest advantage is the userbase for when you have a problem. > > >> - MySQL or Postgresql? > > We use PostgreSQL here because the release quality does not vary > > as wildly and MySQL. Check the mailing list for problems caused by > > particular versions of MySQL. If you pick a tested version, it will > > work well. PostgreSQL also support full text index support that make > > searching ticket body content extremely fast. We also use the Slony > > replication software to keep a warm spare RT system ready to go, in > > case the primary system has a hardware problem. We really want to > > have redundancy in our ticket system because it should be up even if > > everything else is down. :) > > > FTS - is one of the advantages of PostgreSQL we look for. > I am partial to FTS and it definitely rocks on PostgreSQL. Cheers, Ken _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [email protected] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
