Christopher, Thanks for your suggestions.
>How often does your data change? We will be serving up live datasets that change constantly. But to begin with we are expecting to do an update once a week or once a month for each dataset. I will look at your suggestions regardless to see how they might fit the process. Bruce Cheney Gateway Mapping, Inc www.gatewaymapping.com 801.221.7656 -----Original Message----- From: Christopher Schmidt [mailto:[EMAIL PROTECTED] Sent: Thursday, November 08, 2007 4:57 PM To: Bruce Cheney Cc: [email protected] Subject: Re: [UMN_MAPSERVER-USERS] System Configuration - [SPAM] Email found in subject - [SPAM] Email found in subject On Thu, Nov 08, 2007 at 04:30:46PM -0700, Bruce Cheney wrote: > Ed, > > I very much appreciate your help. Very insightful. Yes expectations > are 50,000 users at least at the same time. How often does your data change? You might think about using a tiling client and a tile caching solution on the server if it changes infrequently... TileCache has been known to serve up to a couple hundred requests a second, but that won't provide anywhere near the level of performance you're looking for, I suppose: I've never served more than a steady stream of ~200-300 requests a second with Apache, and that was a pretty unusual circumstance. I recommend you sit down with a single user, have them browse around your site, and track their requests a second. In doing this at MetaCarta, we found that our users using a specific application only generated 1-2 actions every minute -- meaning that with 50,000 users you might be getting down to something sustainable ... I'd personally use OpenLayers and TileCache -- serving up pre-rendered tiles from disk is going to be significantly easier to scale than serving up rendeered data from shapefiles, I think -- but this may just be my lack of experience with serving data fast. Regards, -- Christopher Schmidt MetaCarta
