TECHNICAL SUPPORT / WEB APPs BUGS

Problem: In unregelmäßigen Abständen - mit teilweise extremer Häufigkeit - hängt ryzom komplett.
Anders als bei PW's kann ich nichts machen, weder umherschauen oder Nachrichten tippen. PW's kommen i.d.R. am Ende eines solchen Aussetzers (was nachvollziehbar ist)

System:
AMD 8-Kern 4Ghz (Ryzom benutzt immer nur einen Kern, und den auch auf anderen PC's mit immer fast 100%)
16GB Ram
SSD Raid0
Nvidia Quadro Keplar 2000 (Eigentlich für Videobearbeitung, andere Spiele - eigentlich alles mit DX10/11 - läuft sehr gut)
Win7Pro

Ausschließen kann ich Netzwerkprobleme. Von einem anderen Rechner funktioniert die Verbindung zu Ryzom und zu dem Problemrechner konstant einwandfrei ohne Packet loss und in atemberaubender Geschwindigkeit. Der Ryzom Server liegt dabei mit 200ms im Mittelfeld.
Ebenso kann ich ein generelles Geschwindigkeitsproblem ausschließen.
Was mich fuchst ist, das der Computer einwandfrei läuft, aber nur Ryzom schwierigkeiten macht.
Da die Hardware absolut einwandfrei läuft, und auch andere Software, bin ich mir nicht sicher, wo genau ich einen Fehler suchen sollte. Vielleicht hat jemand dieses Problem schonmal gehabt - und kann mir bei einer Lösung helfen. Gerne besorge ich mehr Systemdetails oder schlage mich mit debuggern herum.

Close, but not exactly. I'm used to PW's, but the actual problem looks like Ryzom fails to work properly with the hardware - or the other way. Basically everything runs well, but Ryzom hangs often. I'm guessing minor incompatibilities, but I have absolutely no clue where to start searching for the problem.
Hanging means that the whole Ryzom client stops doing anything for up to 10-15 seconds sometimes. No screen refresh, no input possible - it just does nothing, but all other active tasks (if there are any) still run fine. I'd say it does something, but it's hard to figure out anomalies since it always uses close to 100% of only one cpu core anyways.
My first suspect was some "AMD overdrive" technology - it lowers the CPU clock if the power consumption gets over a certain level. If I got that right I can set it to "+20%" which actually means the cpu runs on 100% all the time, but it also tells me that I will be doing this at my own risk, so I kept my fingers off of it.
My second suspect is that I'm using graphic hardware that is designed for CAD stuff rather than games - But it is fast enough to run for example LOTRO and ESO with incredibly high detail level and fps, so why would it be a problem for Ryzom?
For now I'm scared to mess with the system, it is new, runs perfect without crashes or even problems, cost a lot of money and I need it for a big part of my work on a daily basis...
I really don't know where to search, all I can think of right now is to throw in some additional information about the hardware and drivers - which I'll take care of tomorrow.
Maybe I just need to lower or limit GPU settings, downgrade some drivers or anything like that.
Any suggestions are welcome

I agree on the possible bad code, but in my case not with the client server sync.
Ryzom occupies about 99% of a core no matter if it's 2 or 4 Ghz, so clearly something is running at full pace which obviously doesn't need to. I'd like it stuck at 80% to have some reserves, but I doubt some skilled programmer can fix that soon - as well as the desired multi thread support.
I have an update about the behaviour tho:
Observing the CPU Graphs I saw that when it hangs the CPU load for that core goes right to the top and stays there, and the kernel times go flat down. Normal business with small moves in the graph comes back when it's working again. Looks similar to other CPU overload problems I've had with other software in the past.
I admit tho that I think Ryzom can cause that with client / server sync problems...
Remarkable is that the last played audio buffers continue playing when everything else about Ryzom stops for a while - so not all of Ryzom is hanging when it hangs.
I have observed similar freezes on all computers I've played Ryzom on, when you go AFK for let's say 10 mins, and then zoom out or look around. As if the graphic card needs to shovel back some data - or something else has forgotten something and has to wait for it to be back. The actual freezes are about the same type of freezes, but they come all the time now on the new PC. The regular PW's are not at all a pain in the ... compared to this.
Desperate as I am I go on with some details about the Hardware:

Win7Pro64 SP1 oem
Kernel: 6.1.7601.18409
DXdiag: DX11 all tests passed
Board: M5A97 R2.0 rev 1.xx
CPU: AMD FX8350 "vishera" 8 core at 4Ghz
Graphic: Quadro K2000 2GB, Driver ver: 9.18.13.4105
Disk: def. fast enough
Mem: def. enough and fast enough
I've had the Keplar monitored in background, it is close to falling asleep with rendering Ryzom.

Gonna check the size of the fans and start playing with that "overdrive" technology tomorrow. Maybe I can deactivate any dynamic clocking - would be awesome if that caused the trouble and I can get rid of it.

People often ask me "did you set processor affinity?"
So... how do you do that?
Don't get me wrong, I know how to do that in general, but Ryzom can't be changed. So all I have ever done is ban all other processes from the core Ryzom is using. I'd love to have Ryzom on more than one core. Where's the trick? I hope it's not a hyperthreading thing - I have 8 real cores, not using intel here...

I have found some simple command-line parameters I will try first. I am still suspicious if you can even spread Ryzom over multiple cores, but I'll post results here later. Thank you all so far :)

Almost as expected the commandline parameters do nothing on ryzom (expl: Ryzom is a single thread application). Other than trying to change it directly in the taskmanager you don't get a notification that it failed or is impossible this way.
Any other suggestions welcome :)

And that brings me back to the start. Ryzom runs on an older and much slower pc fine (except the pw's which I am used to). My solution for now is to stack a few more screens, keyboards and mice on the desk and have the old pc available. But still I wonder - since I can exclude hard- and software problems - where exactly Ryzom fails to get along with the fast pc. I still hope for a simple solution like a bugfix, downgrade or anything like that.
I was wondering lately, if there's some kind of virtualisation method, like perhaps a vm running on 4 cores, with linux, acting as if it only had one core. I'm not sure, if that's even possible, but that is the only way I can imagine right now for having more cores involved for the powerhungry Ryzom. (The dropouts still look to me like an overload problem.)
But who knows... Maybe I'm searching at the wrong end....
I've played LOTRO yesterday. All details at max, shadows looked nice, puddles reflected the sky, trees with high detail far away. Used 4/8 cores, had a peak of 13% cpu usage in a crowded place. Was nice. I wish Ryzom would get at least half way there soon. Even if it's not overload problems I have here - maybe someone can figure out the loop which is causing the cpu load, and do something about it. I bet Ryzom would stay around 5% usage on one core, saving power, preventing noise, making laptop batteries live longer...
My Programming skills got stuck on Basic, ASM, tPascal and Lazarus about 15 years ago, so I can not really contribute anything. But I'm curious how hard it is to implement a second thread beside killing the loop. I can imagine having network and inputs one one side, and the rest of the game on the other. Nudge me, if I start being silly.
Any suggestions still very welcome :)

Good one, but I've already tried everything I could do in the game settings - including reducing audio channels, minimal graphic settings and so on.
Sometimes I think it is weird. I have a PC capable of giving me a good workflow on editing videos and special effects in 1080p, uncompressed streams with a high framerate, but it has problems with ryzom :/
I could probably still blame the Keplar but I'd like that confirmed. Anyone else with a Quadro K2000 playing Ryzom here?
Beside that, the fact that Ryzom tries to fry a cpu core independent from it's clock speed is a sign of bad programming. I used looped requests all the time before I found out how to use interrupts. I don't know how stuff works with the GDT nowadays, but maybe a timer with a few miliseconds could call that ryzom routine and stop it from running at full pace.
I love Ryzom and I'd like it to be playable, so...
Still any suggestions welcome :)