Insil

erm its not a problem to have a multiprocessed server framework aka. a cluster where each process runs more threads n fibers...

People never gave this approach any thought in the past, since you only had 1 core per cpu available hehe... It was also back then where unix sucked with threadhandling and therefore multiprocessing was better...

Multithreading is the way to go honestly... Less IPC, less threadblocking, and some fewer headaches

is there any indexing enabled for the db whatsoever? cuz that would explain some of the crappy select/update performance...

Profilers are able to see across threads by the way. They can measure which threads are eating up the most cpu time etc.

not entirely sure how native profilers work tbh, although im sure they arent as revealing as the .net ones, which can benchmark the amount of time the application spend on each method hehe

"we all know we dump garbage..but you can only take out the trash one at a time while another person drops it off."

great choice of words i must say

You're talking about async db access so the worker thread wouldnt block like it does now... obviously the only way to go for a singlethreaded serverapplication hehe

As i see it, the main issues of mangos have never been adressed. There have been several attempts to work around things, where the common perception seems to be "lets add some opensource framework to the base and hope it fixes the problems" which it obviously dont. I dont know whether this is because of the lack of internal management, but it occurs to me that the real performanceissues are being overlooked, while minor problems blown out of proporsion. Lets face it, mangos has some serious fundemental design flaws that over the years never has been corrected. That ralf guy or whatever he was called, tried to make a patch which would adress the threading issues, although it didnt seem to have been accepted... I'd say mangos has to stop crapping around with minor things and start adressing the real issues which are likely to take a while to rewrite...

Im wondering... Is the thread accessing the DB and the main worker thread the same? in that case, the thread would block whenever it has to access the db like...when chars log in they have to be loaded etc etc... This would put the entire server on hold, and blimey if there isnt some funky thread.sleep involved in that sequence