EVE Search - Boost MSH

All Channels

Corporation, Alliance and Organization Discussions

Boost MSH

» Click here to find additional results for this topic using Google

Monitor this thread via RSS [?]

Author	Thread Statistics \| Show CCP posts - 3 post(s)
Pattonator Federation of Freedom Fighters Executive Outcomes	Posted - 2008.09.27 17:00:00 - [1] Maybe u need to upgrade the hamsters to something larger like guinea pigs.
Pattonator Federation of Freedom Fighters Executive Outcomes	Posted - 2008.09.28 14:29:00 - [2] Originally by: CCP Mindstar Originally by: Gjs312 Originally by: CCP Mindstar Greetings all, Just a quick follow up to let you know what was going on server side with the fleet battles today. Right as the first battle in MSHD-4 commenced, we got our usual notification that the CPU on the node supporting that solar system was heavily loaded. Within a couple of minutes the node had died - somewhat unusual. Over the course of the next hour or so, the node died multiple times, and an analysis of the system logs showed that it was not responding well to the high load. At this point, we re-mapped the fleet battle to one of our new "dedicated" nodes. These were installed recently in the cluster and have around 16gb of RAM, and faster CPU than others. They also run a special 64-bit EVE server (thanks to StacklessIO we can do this now) that allows them to use this extra memory. Once the system was remapped, it seems that the newer hardware responded quite well to the fleet battle, and did not experience the same crashing issue as the regular node did. Our server boffins will be going over the data from this next week, so expect some more juicy information about all this stuff soon. Fly safe, Mindstar Wait.. You guys normally get a notification when a large fleet battle is starting and then decide if you want to reinforce the node or not? Or am I misunderstanding what you are saying. We do have hardware monitors in place that will tell us if CPU or memory, is getting overloaded on a machine in the cluster. Tihs happens most commonly during fleet battles. Usually the course of action is to leave it as is, however there were two things different about the battle yesterday that caused us to decide to re-map it. - Firstly, it was causing repeated node deaths, which is not good and something we very much wish to avoid. We are going to very closely analyse why this was and ensure that it gets fixed asap. - Secondly, we have some newer hardware quite recently installed that we thought would be able to handle it a bit better. With the battle causing lots of problems running where it was on the existing hardware we decided to move it over to one of the new machines and see what happened. I hope that makes things a little clearer. Mindstar Mindstar- Just an FYI but the GM's that handle the petitions are completely unaware that your system can detect or record any large amounts of cpu load or lag. Any petition is ALWAYS answered that the server side logs show no record of lag. In the future I'll forward any lag loss petitions to you.

COPYRIGHT NOTICE
EVE Online, the EVE logo, EVE and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. CCP hf. has granted permission to EVE-Search.com to use EVE Online and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, EVE-Search.com. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.