dante696 Thank you for the explanationOriginally Posted by dante696
i love the CELT but i understand the "why"
We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020
-= TeamSpeak Lover =-
dante696 Thank you for the explanation
i love the CELT but i understand the "why"
-= TeamSpeak User =-
Did you use an old IP location DB for the Beta?
Since the Beta one of my servers (client side) are located at a country where the IP has been 2 years ago. It's a static IP.
http://www.ip2location.com/free.asp shows right location btw.
-= TeamSpeak User =-
same issue here, server was always located in germany (where it is) and now its france. LoL
-= TeamSpeak Addict =-
Totally agreeable, I was contacted while remote about the poor quality on my personal server (coming from other users that also use ts3 daily). Turns out I had my channels on speex. Glad to see them gone.
Also thanks for having a menus to change the codec from mobile.
We will rework the IP database for stable release.
You did something great here by updating your system(s)
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
-= TeamSpeak Lover =-
Thx for repairing the the clientdblist problem!
Using the Query in this case as raw (no SSH), about a PHP script (library of ScP).
With older version
TS3 Server version: 3.5.1 on Linux [Build: 1545076855 from 2018-12-17 21:00:55]
2019-03-03 17:51:38.594568 INFO Get TS3 Clientlist [DONE]
2019-03-03 17:51:38.594521 DEBUG Got TS3 Clientlist 23130 of 23130 Clients.
[..]
2019-03-03 17:41:28.447664 DEBUG Got TS3 Clientlist 600 of 23129 Clients.
2019-03-03 17:41:22.955145 DEBUG Got TS3 Clientlist 400 of 23129 Clients.
2019-03-03 17:41:17.513533 DEBUG Got TS3 Clientlist 200 of 23129 Clients.
2019-03-03 17:41:12.062112 INFO Get TS3 Clientlist...
2019-03-03 17:41:12.062062 NOTICE Scanning for clients to delete...
With current beta
TS3 Server version: 3.7.0-beta1 on Linux [Build: 1551271723 from 2019-02-27 13:48:43]
2019-03-04 08:27:33.724068 INFO Get TS3 Clientlist [DONE]
2019-03-04 08:27:33.724013 DEBUG Got TS3 Clientlist 23142 of 23142 Clients.
[..]
2019-03-04 08:27:31.806470 DEBUG Got TS3 Clientlist 600 of 23142 Clients.
2019-03-04 08:27:31.801499 DEBUG Got TS3 Clientlist 400 of 23142 Clients.
2019-03-04 08:27:31.795683 DEBUG Got TS3 Clientlist 200 of 23142 Clients.
2019-03-04 08:27:31.790817 INFO Get TS3 Clientlist...
2019-03-04 08:27:31.790764 NOTICE Scanning for clients to delete...
-= TeamSpeak Addict =-
They brought down the time for getting all clients by 10 (ten) minutes? To now 2 seconds?
Wow. This is some crazy optimization. Or some very very very bad programming before.
I guess sits the later tbh
-= TeamSpeak Lover =-
No issues whatsoever with the current beta except for incorrect flags for some users, though I see you mentioned it will be sorted in stable release so I guess it's fine.
//Edit
I just noticed, some channels with reached user limit (2/2) do no highlight with red, I never noticed that in stable releases, check it out some are red others are not.
Last edited by Fubister; March 5th, 2019 at 07:53 PM. Reason: update
-= TeamSpeak Lover =-
I can give an additional feedback to the performance of the new version.
Tested with the raw (no SSH) query, with a PHP script (library of ScP).
On old server version (3.6.1) the script needs an average runtime of 0,0793 seconds for one duration.
Without changing anything else, after the TS server update it needs an average runtime of 0,0709 seconds for one duration.
That is a query perfomance boost of ~10,5 %! -> Good job for this!
Sure, with PHP as third party, it is not 100% evaluable. But it gives an approximate trend.
That were the hard facts.
I have one more, but this is only a feeling (haven't measured it accurate), the CPU usage of the server process is lower than before. Would say, it's the half of before! But sorry, haven't any numbers here. Perhaps others can also give a report of their observation.
It's the client doing that. The server only sends the amount of users and the client interface sets the colors and needed icons.
Currently I do not remember why this icon is blue in some full channels. Need to test it when back at my computer.
The CPU usage should be nearly the same as before OR minimal higher when measured.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
-= TeamSpeak Lover =-
Could you at least make a micro update to solve flags issue? ... I think that that is a potential issue...
Don't worry about delaying next release ^^
Last edited by dante696; March 12th, 2019 at 10:37 AM. Reason: moved to right thread
Maybe a beta 2 (without the Cent OS 6 support) will be released today.
That version will fix the ip2ocation database.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
-= TeamSpeak Lover =-
Why need to push a new version to update the ip2location database? Why the server process can't update this database independently?
It's not that we don't want it but we can not do this.
It must be included in the server binary we build for a release.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
-= TeamSpeak Lover =-
Why don't save this information inside the database? You could cache this values and update it from the database every X minutes/hours.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
