All,
Thank you for all your very helpful responses.
A quick update, apologies that it has come a little late.
Firstly I disabled all the caching on each of the layers we had made available
to GWC inside Geoserver.I then removed ALL gwc jar files from the GeoServer lib
directory. I believe last time I may have missed a few.Geoserver started
happily with no errors.
GWCdeployed, I just needed to steal the majority of the text from the layer
config files in the gwc-layers directory.
Afterall, we currently have two servers, one running 4 instances of geoserer,
the other; solely running GWC. Going forward, we are allocating another 3
servers for geoserver and one additional GWC.
To answer the question of requirement, this service is for a national mapping
application serving thousands of clients concurrently, we very shortly realised
that the original design was not going to cut it, especially as the GWC was
consuming a lot of memory as we have complete national coverage of high
resolution base-mapping data. This clashed with the memory allocation for
GeoServer and did result in memory issues.
Overall, a success at this moment in time, I may post back later in the
programme with some performance stats to see if we really have gained a
valuable improvement.
Thank you for all our support
> From: [email protected]
> Date: Fri, 27 Mar 2015 18:58:14 +0100
> Subject: Re: [Geoserver-users] GeoServer without GWC?
> To: [email protected]
> CC: [email protected]; [email protected]
>
> Adding to Andrea's.
>
> We used to deplou GWC separately in the past for a number of reasons:
>
> - diskquota did not work in a cluster hence when we had multiple
> geoserver in parallel using embedded GWC was not an option
> - gwc integration in geoserver was still a bit unstable
> - more control over the configuration
> - easier to scale them independently
>
> As of today we are pushing towards keeping them integrated which makes
> deployments simpler, however there is still one thing on the wishlist
> that would make the integrated GWC my #1 option without doubts and
> that would be the ability to distinguish WMS requests that are routed
> transparently to GWC from those that are not in the control flow
> plugin.
> It is infact impossible today to create a QOS strategy that
> differentiate this use case when GS and GWC are integrate and that can
> be painful when you are serving thousands of users with the same
> cluster. Of course, you can dedicate different groups of isntances to
> different roles but that's not different than using GWC standlone.
>
> Regards,
> Simone Giannecchini
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/NWWaa2 for more information.
> ==
> Ing. Simone Giannecchini
> @simogeo
> Founder/Director
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39 333 8128928
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
> AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate.
> Il loro utilizzo è consentito esclusivamente al destinatario del
> messaggio, per le finalità indicate nel messaggio stesso. Qualora
> riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
> cortesemente di darcene notizia via e-mail e di procedere alla
> distruzione del messaggio stesso, cancellandolo dal Vostro sistema.
> Conservare il messaggio stesso, divulgarlo anche in parte,
> distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
> diverse, costituisce comportamento contrario ai principi dettati dal
> D.Lgs. 196/2003.
>
> The information in this message and/or attachments, is intended solely
> for the attention and use of the named addressee(s) and may be
> confidential or proprietary in nature or covered by the provisions of
> privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New
> Data Protection Code).Any use not in accord with its purpose, any
> disclosure, reproduction, copying, distribution, or either
> dissemination, either whole or partial, is strictly forbidden except
> previous formal approval of the named addressee(s). If you are not the
> intended recipient, please contact immediately the sender by
> telephone, fax or e-mail and delete the information in this message
> that has been received in error. The sender does not give any warranty
> or accept liability as the content, accuracy or completeness of sent
> messages and accepts no responsibility for changes made after they
> were sent or for other risks which arise as a result of e-mail
> transmission, viruses, etc.
>
>
> On Thu, Mar 26, 2015 at 8:06 AM, Andrea Aime
> <[email protected]> wrote:
> > On Wed, Mar 25, 2015 at 11:55 AM, gavin.montgomery
> > <[email protected]> wrote:
> >>
> >> Hi,
> >>
> >> It is commonly mentioned to use a standalone geowebcache instance when
> >> serving multiple geoserver instances and to improve performance in
> >> production environments for a high load of customers. For example the
> >> following blog from GeoSolutions:
> >>
> >>
> >> http://www.geo-solutions.it/blog/real-world-uses-cases-troubleshooting-large-geoserver-deployment/
> >>
> >> <http://www.geo-solutions.it/blog/real-world-uses-cases-troubleshooting-large-geoserver-deployment/>
> >
> >
> > Right, this is one of the few cases in which we still deploy a stand-alone
> > GWC.
> > But look at the numbers, we are talking about thousands of requests per
> > second... in this situation
> > it's indeed a good idea to keep it separate, mostly to avoid the sheer
> > number of requests
> > GWC is receiving to dominate your tomcat instance, and leaving little space
> > to wms/wfs.
> >
> > But if you don't have such a demanding deploy, keeping the integrated one
> > it's easier
> > and it's (by far) the more common choice.
> >
> > Cheers
> > Andrea
> >
> > --
> > ==
> > GeoServer Professional Services from the experts! Visit
> > http://goo.gl/NWWaa2 for more information.
> > ==
> >
> > Ing. Andrea Aime
> > @geowolf
> > Technical Lead
> >
> > GeoSolutions S.A.S.
> > Via Poggio alle Viti 1187
> > 55054 Massarosa (LU)
> > Italy
> > phone: +39 0584 962313
> > fax: +39 0584 1660272
> > mob: +39 339 8844549
> >
> > http://www.geo-solutions.it
> > http://twitter.com/geosolutions_it
> >
> > AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
> >
> > Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i
> > file/s allegato/i sono da considerarsi strettamente riservate. Il loro
> > utilizzo è consentito esclusivamente al destinatario del messaggio, per le
> > finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio
> > senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia
> > via e-mail e di procedere alla distruzione del messaggio stesso,
> > cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo
> > anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per
> > finalità diverse, costituisce comportamento contrario ai principi dettati
> > dal D.Lgs. 196/2003.
> >
> >
> >
> > The information in this message and/or attachments, is intended solely for
> > the attention and use of the named addressee(s) and may be confidential or
> > proprietary in nature or covered by the provisions of privacy act
> > (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> > Code).Any use not in accord with its purpose, any disclosure, reproduction,
> > copying, distribution, or either dissemination, either whole or partial, is
> > strictly forbidden except previous formal approval of the named
> > addressee(s). If you are not the intended recipient, please contact
> > immediately the sender by telephone, fax or e-mail and delete the
> > information in this message that has been received in error. The sender does
> > not give any warranty or accept liability as the content, accuracy or
> > completeness of sent messages and accepts no responsibility for changes
> > made after they were sent or for other risks which arise as a result of
> > e-mail transmission, viruses, etc.
> >
> >
> > -------------------------------------------------------
> >
> > ------------------------------------------------------------------------------
> > Dive into the World of Parallel Programming The Go Parallel Website,
> > sponsored
> > by Intel and developed in partnership with Slashdot Media, is your hub for
> > all
> > things parallel software development, from weekly thought leadership blogs
> > to
> > news, videos, case studies, tutorials and more. Take a look and join the
> > conversation now. http://goparallel.sourceforge.net/
> > _______________________________________________
> > Geoserver-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/geoserver-users
> >
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
