On 4/9/2020 10:24 PM, Keisuke Miyako via 4D_Tech wrote:
Thank you for your reply.
I have an application I'm trying to convert from 4D v17R6 to v18.1LTS. It is
hosted on Windows Server 2016. It was a well-behaved application when running
v17R6 with no notable issues. However, now that it has been upgraded and
running on v18.1 LTS, it takes 10-15 minutes for the application to start-up in
4D Server. Specifically, from the moment that the database is selected from the
Open... menu item until the Server Administration Window appears is between 10
and 15 minutes.
is it possible that the application, for whatever reason, needs to copy all
your database files to a virtual store?
Hmm. I don't know what a virtual store is, so probably not.
---
also, windows server by default has a conservative power plan, which prevents
4D Server from drawing on its full potential.
https://support.microsoft.com/en-us/help/2207548/slow-performance-on-windows-server-when-using-the-balanced-power-plan
https://docs.microsoft.com/en-us/windows-server/administration/performance-tuning/hardware/power/power-performance-tuning
of course, that does not explain why 17 R6 is doing just fine.
The server host is a VM running in a large data center. Interrogating
the Power settings shows nothing that appear would be throttling power,
i.e., all options set to "never sleep", with Power Place set to "High
performance".
---
The same application opens pretty much instantly when running in single-user
mode on my development machine (Windows 10 Pro). So the only difference is host
application (4D Server) and OS.
what about the hardware?
more specifically, do you know if the storage is HD or SSD?
Running on VMWare, as above. I don't know exactly how the VM has been
provisioned, but we're hosted in a university data center with some
resources. Disk Management reveals nothing about the hardware
configuration except to say "VMWare Virtual Disk" for each volume.
I would rule out the OS being an issue since the same application ran fine on
the same host machine and opened with no delay just prior to the upgrade from
v17R6 to v18.1LTS.
have you tried to launch 4D Server on your dev. machine, Windows 10 Pro,
to see if the correlation is really linked to the application type?
and just to rule out that the issue is not application specific,
you might want to compare the time with a fresh 4DB.
Well, your question promoted me to re-convert the database on the server
host. Previously I had converted to v18.1 on my desktop development
machine and also converted from binary to project database. So, I have
now opened a fresh copy of the v17R6 database with v18.1 LTS on the
server itself. It opened pretty much instantly after the conversion
warning dialog. I then closed and re-opened the database several times
in succession, each time with no delay.
So, my conclusion is that converting the database to a v18 project
database is the performance killer. Which is mildly annoying, because
the project database format was a most significant reason why I wanted
to upgrade, since it is a really appealing feature. But apparently it
still has some major flaws.
So, now knowing that the project database aspect is the problem, is it
worth reporting a bug? Or would it be best to just wait for a few more
iterations of v18 for this feature to mature?
Many thanks again for your assistance.
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
