> > > DBIC::Cursor::Cached WILL get you a performance boost no matter what! We > haven't seen a worrying drop in performance since using it. >
you didn't understand me. From the database side - you WILL get a perfomance boost. but from LOCAL side (server where your backend is) you WILL LOSE perfomance (~ 2x slower). Your perl program will take more CPU TIME (not wallclock time) than without Cursor::Cached at all. I meant that my solution will get you a perfomance boost at both - perl-side and db-side > > > I have 5-7mln page hits per day. When i tried to use > DBIC::Cursor::Cached, > > users were about to blow the server up. > > Hits are not representative to boast with the performance of your Catalyst > application (http://en.wikipedia.org/wiki/Page_view). What percentage of > those > hits are static files like images, css, js, etc which you shouldn't be > serving > through catalyst anyway? 80%? > > --Tobias > I ment 5-7mln pure requests to catalyst backends (without any static). > > > _______________________________________________ > List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class > IRC: irc.perl.org#dbix-class > SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/ > Searchable Archive: > http://www.grokbase.com/group/[EMAIL PROTECTED] >
_______________________________________________ List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class IRC: irc.perl.org#dbix-class SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/ Searchable Archive: http://www.grokbase.com/group/[EMAIL PROTECTED]
