cycling4freaks.com

Ich muss mal on sein wen ndas passiert und direkt auf dem Server nachschauen ob da irgendwelche Prozesse nicht geschlossen werden oder wo da der Engpass sein kann. Wenn der Server wirklich einfach überlastet werden soll muss ich halt aufrüsten.

Bei mir gehts übrigens wieder.
Ohne das ich da was gemacht habe. Wer weiß was die Leute von der IT-Abteilung da rumgebastelt haben

Ehm, posted this into a completely wrong thread at night. Now I moved it here:


And another lagging connection around km 86. CIrduit de Lorraine.

Now it started at km 84, 21:34h, and lasted until km ~93. This time not so bad as the last 2 days. But still remarkable, 3 days in a row at exactly the same time.

Yes, i read this post, too.

I will look what the problem is and upgrade the server if necessary.

I will upgrade the server. And maybe make a limit for refrehsing every 5 seconds or anything like this. Definitly too many connections in one moment.

Do you think because of the new design the race is refreshed more often than in the old design?

Buhmann wrote:I will upgrade the server. And maybe make a limit for refrehsing every 5 seconds or anything like this. Definitly too many connections in one moment.

Hm. You mean only actualization, not changing tempo or attacking settings?

Do you think because of the new design the race is refreshed more often than in the old design?

Maybe there are more klicks on the various special classification because the points or no longer shown directly in the race screen..

And yes, the auto-refresh option probably leads to more often actualizations then without, even though maybe only few users use it.

Hm. You mean only actualization, not changing tempo or attacking settings?

Yes, only refrehsin the race.

Maybe there are more klicks on the various special classification because the points or no longer shown directly in the race screen..

This is not a problem, because for this is no server-request necessary.

Ok. But nonetheless I guess the new designs demands more load for opening tactic windows, loading and saving every single helper, fighting, following etc; one by one instead of 5 settings at once and then saving the tactics as a whole, as it was with the old design.

The only problem is the refresh. The other things are not often enough to make problems. At important situations ( a hill or somethink like this) there are too many requests. And the reason for this should be the clicks on the refresh button. But this all should be a problem which i can solve. With some tricks. server configuration and server upgrade.

Ok, understand.

One trick could be: no tempo change in the last 5 secs before the next km calculation and by that way surpressing sec tricks Then no one has a reason to refresh hundred times to see if somebody tricks himself in or out of tempo in the last moment, forcing to set or unset a planned attack.

Btw is there still this +/- 3 secs random margin for calculation of the next km as it once was installed for reducing sec-tricks?

Yes, there is such a random margin.

And yes, this is the only problem. I could avert that every user so often on the refresh button (yesterday i have integrate a 2 seconds limit, before it was 1). A 5 seconds limit would be meaningful, too. But the the sectric then is even more useful.
We could integrate a 5 seconds delay for the tactic-functions, so that the problem would be solved. Not sure, if the server problem would be solved, too. But better anyway.

5 seconds delay? For each possible tactics setting? You mean I click on Tempo and it changes only 5 seconds later? The same with attacking, fighting, following...?

Okay, only for the tempo-function it makes really sense. Like you said. If you cklick tempo, there would be shown "ride to the front.." (only for the team of this rider, the others wouldn´t see this, technical reasons). And after 5 seconds there is shown "Tempo" like now. Only a weapon against the sectric.

Hm. It could also be used as a tool for sec-tricking. I mean, what's the difference between clicking half a second before the km change and clicking 5 seconds earlier? For the pontential attackers it stays the same: they see a situation, they set an attack, but suddenly a rider appears in tempo short before the km change.

And should it be the same delay for changing the colour of the tempo?

You are right

The others have to see the "ride to front"

Changing color must be the same...but okay, is more complicated now...

Buhmann wrote: The others have to see the "ride to front"

Oh yes, that would help!

Nobody hast to see anything what i do as long as i can't react immediately to an escape.

And signalizing 5 seconds before that I am going to change the tempo mode freom green to red would be a bit strange. I still consider forcing the teams to make their tempo settings until 5 secs before km change the better solution. Then the margin of the km change could be thrown out, too.

And as Zentaron said, the next necessary step would be the yellow tempo, or however it should be managed to give the chasers the chance to reduce the gap of on attacker.

Today, yesterday (belgium tour) and at least the last 3 stages of my previous stage race the connection lagged more or less exactly at km 86 for around 5-10km...

That can't be because of traffic. It's always at the same point of a stage. And not only since the new design is on air...

So now the problem came to me too.....pages don't load any more while playing in german language. Everything works fine again after switching the language to english.

Hope the german version will work again soon....

Does the dutch version works for example?
Maybe delete the cache and try again. Can you solve the problem with that?

Anyonbe else who has problems with loading in a special language? Need to find out if it is a cahce problem or a technical at my side.

Buhmann wrote:Does the dutch version works for example?
Maybe delete the cache and try again. Can you solve the problem with that?

Just tried them all. Only the german version causes these problems...

Deleted the cache? I think you have the old labels in the cache.

is it working now??