В эти дни я по его слвам понял что он переносит легеон тоесть его систему как он написал на другое железо

Сайт сервера запахал. Кто-нибудь находил там что-то по поводу Легиона?

Letme explain a couple of things about things: [Note: if u don't like technical explanations stop reading ] - Downtime: I know ppl may not have enough with msgs like "legion will be back in some hours", but u should understand that most of the times we don't really know how much time will maintenances take, for example the recent 23hrs (or so) downtime: i was moving legion to the PTR pc (which runs on linux) coze as i have been researching (and anyways i knew that before) mysql performs better on linux and the rollbacks that legion was suffering was due to db queries not running fast enough so the mysql queues got full and the sqls could never get executed. So i started moving the dbs onto the PTR pc, smth that i expected to take 2 hours more or less (tho i knew it could take more), but sadly for u and me the dbs are huge and they were taking a LOT to load, so after a few tries at around the hour 21 i decided to move the entire files instead of a sql dump, that worked like a charm, so dbs got moved and the rest was setting up the confings and stuff. After that legion was up but smth that i expected to take 2 hours took me 23 hours instead, so would u prefer to hear "legion will be back in 2 hours" and later "sry, it will take 10 hours" and even later "sry again, it will take 23hours", i wouldn't, coze u would thing i'm playing with u, so the msg "legion will be back in some hours" is more likely to be true even if it's vague since no one can predict how much time things will take sometimes. - Lag: After i moved legion on to the linux pc i was expecting it to be lag free as well, sadly i was wrong, so after some tests (a few restarts to add debug r1197/r1200) i found out map threads was executing a lot of sqls and some of these sqls were delaying too much, and thus lagging the hell our of the server, coze if something doesn't ends soon the server <=> client communication delays for a few secs or sometimes more. So after this research i implemented a few funcs to help with this (r1201), and after that everyone said lag was mostly gone (and my logs say so, tho there are a few lag spikes left that i'm working on atm), so luckly lag is doing better now. - Loops: This is something really obscure and very technical (even more than lag explanation lol), so if u're still reading this post u're either crazy or u know what a lock in c++ means, servers runs many threads (one per each map and a few more for other things, like db stuff, etc), each thread run in parallel so when ie. one thread accesses the player list it must lock it before doing that coze if another thread does that at the same time bad things could happen, if it wouldn't lock it. So this locks are complex and they're all over the code, but sadly there is still some bug with them that i've been trying to find out but i haven't yet, so sometimes one of these locks get locked but never unlocked, and what happens after this is ppl spamming over the forum saying "qq legion is looping plx restart it" as u all know it happens. I'm sure i'll find this bug in time, but until my brain figures it out we'll have to live with loops, hopefully we can do that in the meantime I'm sure no one is still reading lol so here's my explanations of legion latest probs, this post took me like 20mins :/ i'm finishing a commit right now, and i need to get some sleep too, so, hope this helped to show u some light , cya. Вот что сказал марселло по поводу легиона,как я понял его переводят на машину ПТРа

Letme explain a couple of things about things: [Note: if u don't like technical explanations stop reading ] - Downtime: I know ppl may not have enough with msgs like "legion will be back in some hours", but u should understand that most of the times we don't really know how much time will maintenances take, for example the recent 23hrs (or so) downtime: i was moving legion to the PTR pc (which runs on linux) coze as i have been researching (and anyways i knew that before) mysql performs better on linux and the rollbacks that legion was suffering was due to db queries not running fast enough so the mysql queues got full and the sqls could never get executed. So i started moving the dbs onto the PTR pc, smth that i expected to take 2 hours more or less (tho i knew it could take more), but sadly for u and me the dbs are huge and they were taking a LOT to load, so after a few tries at around the hour 21 i decided to move the entire files instead of a sql dump, that worked like a charm, so dbs got moved and the rest was setting up the confings and stuff. After that legion was up but smth that i expected to take 2 hours took me 23 hours instead, so would u prefer to hear "legion will be back in 2 hours" and later "sry, it will take 10 hours" and even later "sry again, it will take 23hours", i wouldn't, coze u would thing i'm playing with u, so the msg "legion will be back in some hours" is more likely to be true even if it's vague since no one can predict how much time things will take sometimes. - Lag: After i moved legion on to the linux pc i was expecting it to be lag free as well, sadly i was wrong, so after some tests (a few restarts to add debug r1197/r1200) i found out map threads was executing a lot of sqls and some of these sqls were delaying too much, and thus lagging the hell our of the server, coze if something doesn't ends soon the server <=> client communication delays for a few secs or sometimes more. So after this research i implemented a few funcs to help with this (r1201), and after that everyone said lag was mostly gone (and my logs say so, tho there are a few lag spikes left that i'm working on atm), so luckly lag is doing better now. - Loops: This is something really obscure and very technical (even more than lag explanation lol), so if u're still reading this post u're either crazy or u know what a lock in c++ means, servers runs many threads (one per each map and a few more for other things, like db stuff, etc), each thread run in parallel so when ie. one thread accesses the player list it must lock it before doing that coze if another thread does that at the same time bad things could happen, if it wouldn't lock it. So this locks are complex and they're all over the code, but sadly there is still some bug with them that i've been trying to find out but i haven't yet, so sometimes one of these locks get locked but never unlocked, and what happens after this is ppl spamming over the forum saying "qq legion is looping plx restart it" as u all know it happens. I'm sure i'll find this bug in time, but until my brain figures it out we'll have to live with loops, hopefully we can do that in the meantime I'm sure no one is still reading lol so here's my explanations of legion latest probs, this post took me like 20mins :/ i'm finishing a commit right now, and i need to get some sleep too, so, hope this helped to show u some light , cya.

Позвольте мне уточнить несколько вещей: я знаю, что людям недостаточно сообщений типа "Легион будет онлайн через пару часов", но надо понимать, что в большинстве случаев мы не знаем, сколько времени будет потрачено на техническое обслуживание. Например, в последние 23 часа я перемещал Легион на PTR PC (комп, на котором работает тестовый сервер), который работает на Linux. Под Linux MySQL выполняет операции лучше. Поэтому я начал перемещение БД Легиона на PTR PC. Я ожидал, что перемещение займет не более двух часов, но к сожалению, БД просто огромны и я не хочу говорить, когда это будет сделано, потому-что некоторые вещи могут потребовать очень много времени.

ЛАГИ: После того, как я переместил Легион на Линукс, я увидел, что карта нитей SQL выполняла слишком много запросов и некоторые из запросов выполнялись очень долго, из-за чего сервер офигенно лагал. Итак, после этого исследования, я реализовал несколько функций для исправления ситуации, и после этого многие стали говорить, что сервер начал меньше лагать.

LOOP (ЗАЦИКЛИВАНИЕ): это нечно весьма странное (тут текст про С++, SQL и про то, как это все сложно и запутанно). Вобщем эшибки, изза которых возникает "loop" найти очень сложно. Пока-что от циклов нам не удастся избавиться, придется просто рестартить сервер при необходимости (напомню, циклы - это когда не проходит авторизация или очень долго заходит в игру).

А сейчас мне очень надо немного поспать, надеюсь я объяснил вам что-то, удачи.

Люди А реалмлист тотже остался?

Эм а что до этого сервер был не на юникс системе?лол)))

Скорее всего был на "Форточки'98"

Вот я вас не пойму че вы на марсело гоните??????? Без етого чела шас бы серв рухнул! в кой то веки нашли норм програмера!! он как раз делает свою работу просто не успевает так как он 1!!! а как раз остальные сидят и дрочат на свои шмотки!