At 03:08 PM 11/28/01 -0500, Jeff Johnson wrote: >I'm looking at moving our high traffic site to Webware and need to >support clustering. I plan to use PostgreSQL on a dedicated server with >two or more servers running Apache/Webware. Using Sequences to generate >primary keys should handle the issue of creating unique primary keys >across servers. I figure session variables will have to be stored in >the database by __SID__ and fetched for each request in the awake call? >Has anyone attempted this with Webware yet? What other issues will >arise? > >Thanks, >Jeff
Another easy option that someone on the list suggested a while back is to have a front-end box that redirects the user to one of a pool of machines. For example, if the user tries to access http://www.foo.bar then a script (maybe just a simple CGI) redirects the user to one of three WebKit servers http://www1.foo.bar, http://www2.foo.bar, or http://www3.foo.bar. From then on the rest of their session stays on that one machine using Webware's standard in-memory session storage. This won't necessarily balance the load quite as evenly as a more sophisticated solution. But it is really easy to implement and reduces the load on the database server since it won't have to act as a session store. If I had to scale to multiple boxes for performance reasons, this is the strategy I would implement first, since it seems like it's by far the simplest option. -- - Geoff Talvola [EMAIL PROTECTED] _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
