On Tue, 25 Feb 2003, Fred Moyer wrote: > 3) XML compatibility - yes I could use mason as a filter like you > suggested but I'm still limited by the performance constraints of the > component structure. I'm hoping to use server-side includes or something > similar with Axkit to emulate this kind of template structure - I'm sure > it will be more work but I'm at the point where I need to process > thousands of requests per second as opposed to hundreds and integrate with > other vendors using xml standards. Axkit seems to be the 'big kids' Mason > equivalent.
While we the developers are extremely flattered by this, I have severe doubts about reaching the thousands of request/sec mark. I have a pretty funky AxKit app here that has to scale (possibly to millions of users) but I'm achieving that via sensible partitioning, not via a fast AxKit. FYI, with no tuning whatsoever (either to Apache, or PostgreSQL) on a page that does no SQL, but does run through some XSP code, I get about 16rps. "Static" content running through axkit on similar hardware gets about 120rps. I hope you have a lot of machines ;-) -- <!-- Matt --> <:->get a SMart net</:-> Spam trap - do not mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
