steve-ks Posted February 9, 2018 Share Posted February 9, 2018 (edited) Dear all, so after switching from bananian to armbian around half a year ago, I've made several updates to the bananapi server running. As the prototype server is still running with bananian, some problems just occured as I am now testing a fresh install of my web-package, including nginx, mysql, php7 / laravel and some other stuff. So what I realized was that the database, even on a fresh install, is extremely slow. I thought the newer setup with debien stretch and mariadb 10.1+ might be the problem, yet running the same on the older armbian jessie build did not change anything. I also set up a fresh virtual machine running debian stretch with two cores, 1GB of ram imitating a bananapi board. I've created a database, loaded in a mysql_dump file (around 650 lines including comments) and checked the time. Took less than 3 seconds on the virtual machine, on the old bananian image running on our prototype server this file takes 5 seconds. With a fresh armbian installation (downloaded newest image two hours ago) running on the same hardware the dumpfile takes something like half an hour. The SD cards are fine, I tried different ones. The mariadb configuration is exactly the same as the one a fresh debian package uses. The only problem I can still think about might be some disk I/O or permission problems with armbian. Does anybody has any suggestions here ? Actually this problem makes the whole setup not usable anymore. A full database restoration process running normally in less than a minute now takes an hour. Here are the MariaDB variables from the database, though I did not change any configuration. Thanks for any help ! Edited February 9, 2018 by steve-ks Link to comment Share on other sites More sharing options...
Igor Posted February 9, 2018 Share Posted February 9, 2018 There are some problems with the latest update and we are currently investigating them. Read this ... and try the same test with the latest nightly kernel. Link to comment Share on other sites More sharing options...
steve-ks Posted February 12, 2018 Author Share Posted February 12, 2018 Thanks for the info. That's good to know. I'll test the nightly build and keep you informed. Saw in the other thread that you were doing lots of work during the weekend, thanks for that ! Link to comment Share on other sites More sharing options...
Igor Posted February 12, 2018 Share Posted February 12, 2018 18 minutes ago, steve-ks said: I'll test the nightly build and keep you informed. Actually, you only need to update. The stable repository has been updated since some other problems were fixed. apt update & apt upgrade + reboot Link to comment Share on other sites More sharing options...
steve-ks Posted February 12, 2018 Author Share Posted February 12, 2018 So far I retried everything, from nightly build upgrade to completely reinstalling (with database files removed) mariadb server. Right now it does not seem that anything changed. Yet I can break the whole issue down to the database storage engines. I activated profiling and checked for the database routines consuming all the time. There are some problems in closing tables when there are table modification queries, e.g. creating a table. I checked out the average table creation time for following combinations of system, database and db-engine: So as for bananian the same problem occurs after updating the database this does not seem to be an armbian problem. Yet this is still a very strange behavior. I am wondering if there is a problem with the sunxi-headers. For the moment my solution seems to switch to MyISAM tables. Link to comment Share on other sites More sharing options...
Recommended Posts