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.

[jdaviescoates]

@superhua have you tried another browser, incognito tabs, no plugins, cleared cache etc yet?

[robi]

@superhua You edit the .yaml file from the File Manager or CLI console.. then test your page copy.

It might help to fully describe exactly what you're doing to copy a page and how slow it is, so it can be tested on the demo server as well.

[superhua]

@jdaviescoates Yes, I tried …

• Chrome
• Private browsing
• Minimal plugins (e.g., Admin2, API, Login)
• Clearing cache

… but no difference.

Copying a page in Admin2 is still slow.

Thanks for your reply!

[superhua]

@robi Forgive the basic question, but which .yaml file?

I'm using the copy page button in Admin2 to copy:

It takes 12-16 seconds before I can edit the new copy on the Dockerized version.

In contrast, on the same server, the LAMP version takes ~7 seconds.

The demo server was faster, but yielded similar results (i.e., faster on on the LAMP install).

Thank you!

[robi]

@superhua you mentioned it in a previous post with the cache settings. Which other could it be?

[superhua]

@robi Indeed, I did mention grav-system-info.yaml

However, that file is a generated when you click Export YAML under Configuration > Info.

IOW, I don't think you can edit it and affect the system.

I diid add opcache.revalidate_freq: "60s" to php.ini found at /app/data/. But this didn't speed things up.

[robi]

@superhua good to verify.

Find an issue upstream or file one?