We have a test server running Servoy Application Server which takes ridiculously long time to import solutions. The server hardware is not top-of-the-line but is still more than adequate to handle the task. Once the solution is imported, everything works fine. Standard database maintenance is performed on a regular basis for the servoy repository database and other servers with comparable hardware and load are working just fine. The only difference is that this particular test server has been using the same servoy repository database for a couple of years now and more than 450 versions of the same solutions have been imported into it. On multiple occasions we have deleted the solutions using the Servoy Admin page, however looking in the database, I can still see records referencing the old deleted versions of the solutions. Why does Servoy keep in the repository_server database data for deleted solutions? I would expect that when we use the option “Delete All Solutions” from the Servoy Admin page, all data related to the deleted solutions would be deleted as well, however this does not appear to be the case. Could this old and unusable data be causing the extremely slow solution import? Also, on some occasions after we delete all existing solutions from the server, restart the server and use the option “Clean Import” when importing the solutions again, the import log shows an error “Import Failed - the solution xxxxx already exists”, however the import continues and eventually everything is imported successfully. Again, I think that the left-over data from the deleted solutions could be causing this issue.
Has anyone else experienced similar issues? Does anyone have any suggestions on what could be causing this behavior and how to resolve it?
I did have the problem of long import times. I resolved by removing the repository and recreating it, but I was later told that using the compact option would also improve the imort times. But given your problem of old data of deleted repository, I think your best option is to remove the repository and recreate it.
Harjo:
Yep, we clear the repository after every 100 imports/versions, after that it is fast & snappy again.
In my opinion, there should be an option in the Servoy Admin page to do this, instead of having to do it manually. Also, the “Delete All Solutions” should be deleting the data from the database instead of leaving it there orphaned.
One other thing which we noticed is that the import is much slower when we are not logged in directly to the server but connected to it via Terminal Server/Remote Desktop. All operations are performed on the server with local files, just the session is not through the server console but over RDP.
rossent:
One other thing which we noticed is that the import is much slower when we are not logged in directly to the server but connected to it via Terminal Server/Remote Desktop. All operations are performed on the server with local files, just the session is not through the server console but over RDP.
this is very weird and doesn’t make much sense
except maybe that the RDP network takes so much bandwidth that the connection to the db server is just having less? Or is the DB server on the same machine?
But RDP isn’t using that much so that would surprise me.
And for the rest it is just a tomcat server where you talk to from a browser running on that machine. And if the solution file is uploaded it even has that completely locally. So i can’t think of 1 more reason why a RDP session would be so much slower they just have nothing to do with each other