Hello,
given we still have load issues on our main web server (kermit), and all
approaches to fix it didn't work out in the end besides some little
curing, I propose we go for another server, as throwing hardware at the
problem seems to be part of the solution.
We have two choices for that:
(1) Moving the SQL server to kermit completely.
(2) Moving only the Silverstripe instance for www.libreoffice.org and
native language projects to it.
My preference currently is #2. Reasons:
(a) When one of the servers has problems or goes down, it does not
affect all services. If a SQL or web machine is down, it affects all
services, even if the counterpart is still running.
(b) With the web site relaunch project, we need a testbed and second
instance to "pull the plug" when it's ready anyways, and IMHO it makes
sense to have the whole package on a dedicated machine.
(c) Internal connectivity at our ISP is between 200 Mbit/s to 1 Gbit/s.
I am not sure if the sheer amount of SQL data we need in parallel fits that.
Thoughts?
Florian
--
To unsubscribe e-mail to: website+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted
Context
- [libreoffice-website] ordering another server · Florian Effenberger
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.