The following warnings occurred:
Warning [2] Trying to access array offset on null - Line: 198 - File: inc/plugins/google_seo.php PHP 8.3.36 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo.php 198 errorHandler->error_callback
/inc/plugins/google_seo/redirect.php 131 google_seo_tid
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Undefined property: DB_MySQLi::$google_seo_query_limit - Line: 232 - File: inc/plugins/google_seo.php PHP 8.3.36 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo.php 232 errorHandler->error_callback
/inc/plugins/google_seo/redirect.php 131 google_seo_tid
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Decrement on type null has no effect, this will change in the next major version of PHP - Line: 232 - File: inc/plugins/google_seo.php PHP 8.3.36 (Linux)
File Line Function
/inc/class_error.php 157 errorHandler->error
/inc/plugins/google_seo.php 232 errorHandler->error_callback
/inc/plugins/google_seo/redirect.php 131 google_seo_tid
/inc/class_plugins.php 142 google_seo_redirect_hook
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once




r245 question
#1
In revision 245 the log message states:
Quote:Author: madmaxoft: MTRand class is not created in each tick, therefore much improving tick-thread time (now uses ~5 % CPU instead of one full core)

This sounds like a massive improvement but is it? How should I interpret the message above?
Reply
Thanks given by:
#2
I'ts not really massive, but still is quite a lot Smile

On my QuadCore, the tick thread was hogging one core all the time (-> 25 % total CPU) before the change. After the change, the thread is using only about 5 % of the total CPU. Both values were measured with 1 player on the server, 17 chunks viewdistance.

This means that it now runs at least 5 times faster, maybe even more, because a thread can't run faster than one-core-at-a-time.

Note, however, that this was a debug build. In a release build this needn't be so noticable.
Reply
Thanks given by:
#3
It was even worse on Linux before, because the Linux version of MTRand reads a file each time it's createdTongue
Reply
Thanks given by:
#4
That _does_ sound massiveBig Grin
Reply
Thanks given by:




Users browsing this thread: 1 Guest(s)