Grav 2.0 - copying a page is slow

[robi]

Does grav on the demo server have the same pattern?

[superhua]

@robi – Good idea!
Yes, after installing Grav and LAMP (and then Grav on top of that), LAMP/Grav is still faster on the demo server.

[robi]

@superhua perfect for @james to take a peek.

Drop the app subdomains of the demo server to help him out.

[superhua]

@james Here are the two test sites:

• Grav in Docker

• Grav on LAMP

(PM me for password.)

[nebulon]

If both those apps are installed and using the same disk, I can't quite see how filesystem operations would in any case impact how Grav is serving up files. On top of this, the Grav package is also using apache to serve up the files.

[superhua]

@nebulon Thanks for the reply.

Yes, both apps are installed and using the same disk.

Good to know the Grav package is also using Apache.

Quite a mystery why there is a difference in speed then!

[superhua]

Would the following making any difference?

grav-system-info.yaml from the Dockerized install has opcache.revalidate_freq: "2s"

while

grav-system-info.yaml from LAMP install has opcache.revalidate_freq: "60s"

?

[james]

Hello @superhua
The official docker image of grav is also settings this to 2s.
See: https://github.com/getgrav/docker-grav/blob/89920ea92715261adee817dc7d74f366621af5c9/config/php-grav.ini#L32

[robi]

@superhua change it and test?

How's the CPU usage for both during the op?

[superhua]

@robi Thanks for the reply! No, I haven't changed the opcache.revalidate_freq as I don't know how. If there is a way to do that in Cloudron, please let me know.

CPU usage for both is okay -- but the Disk I/O is quite different: 4.6 GB / 9.6 GB for Docker and 128 MB / 436 MB for LAMP:

Docker:

LAMP:

[superhua]

Update: just re-tested on the Docker install, and the I/O amounts are now similar to the LAMP install.

However, copying a page in the GUI is still slow.