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




Multicore
#1
Hey there new here

I just found Cuberite and think it could solve all my problems ever with MC servers (performance).

However, after compiling on my old Test server on the first run it took 82seconds to  start, since it would only use 2 of my 16 Threads for world generating / Chunk loading.
My test server is an old IBM x3850 with 4 dual-cores fitted with hyperthreading.

Is that normal or did I overlook something? Since I  started searching for other server file options b.c. java wasn't using my cores enough.



Cheers
Reply
Thanks given by:
#2
Hey, welcome to the forum.

For every world Cuberite creates threads for the following:
  • Lighting
  • Chunk Storage
  • Chunk Generation
  • Chunk to client communication
  • Ticking

Naturally some threads are more active than others. The heaviest being world generation, but that thread is only active when needed.

The reason why the first run took longer is because it's generating the spawn for all 3 default worlds (overworld, nether and the end). The second time it doesn't have to generate the worlds. It can just load them from storage.
Reply
Thanks given by:




Users browsing this thread: 1 Guest(s)