Completed The process TeaSpeakServer [AsyncSqlPool0] loads the system (1.2.31-beta-2 ).
- Thread starter Vafin
- Start date
Hmm property the cause of the full sync mode which has been changed with the last build to prevent data loss. Actually this is just a relative graph. How much cpu load does it costs at all?
Vafin
TeaFanatic
This problem lasted for an hour, then stopped. The value of IO reached 99% according to the iotop report.
No, i have some problem.
extension settings should not be reset?
What kind of problem?
hmm :/ And the beta 0 was okey for you?
Vafin
TeaFanatic
On 1.2.31-beta-0, I did not notice this.
Hmm okey, well its probely the sqlite full sync think.
I think I'll make that configurable and let the user decide:
1) More performance (May data loss on crash)
2) Less performance (Secure data storage even on crash, or power failure)
I think I'll make that configurable and let the user decide:
1) More performance (May data loss on crash)
2) Less performance (Secure data storage even on crash, or power failure)
What for? we are going to stability. Better to be safe data storage
Well but when its this big of an impact on the aspect of performance
Yes, while it works better than previous versions
Already 10 days everything works without problems. Unexpected crashes and reboots are not observed. CPU consumption is acceptable (used an optimized build). Strains only the consumption of RAM, which sometimes jumps, and as I noticed in Prime time, when appears online, and after, when users leave the server memory is released, but not immediately, but after a while, when online small.
The server can have 10 users online, and the RAM consumption is large, but after a while the consumption is stabilized. I don't know why this is happening.
The server can have 10 users online, and the RAM consumption is large, but after a while the consumption is stabilized. I don't know why this is happening.
Well actually I think this is caused by the "big" packets with are roundabout 400 bytes per packet which cause this behavior.
May I cache these allocated buffers and reuse them. I'll see, thirst I'm currently working on the web client and the native client.
May I cache these allocated buffers and reuse them. I'll see, thirst I'm currently working on the web client and the native client.
That is, you want to say that in the near future server changes should not wait?
I dont really got the gist out of your sentence, but for me the server and the client are both important.
And its one same process of development.
Of cause sometimes the focus falls on the client or the server, but nothing get lost or ignored, specially when there are some critical bugs etc.
And its one same process of development.
Of cause sometimes the focus falls on the client or the server, but nothing get lost or ignored, specially when there are some critical bugs etc.
//Closed due to inactivity (I also think that this has been resolved 
)
)