This might be of interest to some of you.
Best wishes,
Suchith Anand
Dr Suchith Anand
Centre for Geospatial Science
The Nottingham Geospatial Building
University of Nottingham NG7 2 TU
Tel: (0)115 84 32750
http://www.nottingham.ac.uk/cgs/cgs_suchith_anand.html
Hi all,
I saw the following on another mailing list I am on thought I'd post
it here in case any Climate Plugfest people are reading:
-8---8
GovHack is a free, intensive day and a half exploring ways of creating
mashups and
http://www.punkish.org/Raw-Data-vs-Interpreted-Data/
Really, only 5 questions, almost no thinking required. I will give you
your money back if it takes you more than a minute to answer.
So, no matter what your field of study, research or work, please take
a few moments to answer the questions at
For those that did not make it to Sydney, here is the WMS Performance
Shootout presentation with results (GeoServer vs MapServer):
http://www.slideshare.net/gatewaygeomatics.com/wms-performance-shootout
MapServer: power users who manage MapServer sites with high loads/map
draws should
take
Anyone know why Mapguide OS wasn't represented? I'd be happy to set one up
if there is a conference in my area (Seattle/Vancouver BC area).
Craig
-Original Message-
From: discuss-boun...@lists.osgeo.org
[mailto:discuss-boun...@lists.osgeo.org]
On Behalf Of Jeff McKenna
Sent: Friday,
Unfortunately, no one stepped up to represent mapguide.
Cheers
Paul
On 2009-10-23, at 9:28 PM, Craig Miller wrote:
Anyone know why Mapguide OS wasn't represented? I'd be happy to set
one up
if there is a conference in my area (Seattle/Vancouver BC area).
Craig
-Original
It was really interesting. The very close results suggests to me that the
bottlenecks were external to the WMS and more related to external
limitations like the ability to supply things like I/O. It would be
interesting to have profiling data on where the response time was spent. For
Mapserver
I agree wholeheartedly. It looks like the bottleneck was the database.
I've been privy to some MapServer tests done by testing teams over several
months and the result there was always deploying the data with long update
cycles to the middle tier disks instead of using the database. Only then
Craig Miller ha scritto:
I agree wholeheartedly. It looks like the bottleneck was the database.
I’ve been privy to some MapServer tests done by testing teams over
several months and the result there was always deploying the data with
long update cycles to the middle tier disks instead of
Hi list,
today I was at the code sprint in Sydney, and after a whole week of
conference with the associated beers and late nights, nothing much
productive came out of me unfortunately, which was to be expected.
So for next year in Barcelona, I would really appreciate it if the code
sprint
10 matches
Mail list logo
