Files take a long time to load in editor

ℹ️ Support
1

I am using Nextcloud 24 on Cloudron and the Collabora Editor on the same server running as another Cloudron app.

I have a file which is 18 pages long and contains pictures, but has a whole file size of 297 KB. This file takes a huge amount of time to load - I need to scroll through the whole file and wait for everything to load for a long time.

Both apps are running on a dedicated server, so processor power shouldn’t actually be the limiting factor. Which screw can I turn to make the document load faster?

EDIT:
I studied some logs of the editor and found some of these error messages:

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297249 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:3072:122880:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297361 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:12288:122880:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297370 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:0:125952:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297376 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:3072:125952:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297382 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:6144:125952:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297388 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:9216:125952:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297393 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:12288:125952:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297399 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:0:129024:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297404 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:3072:129024:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297409 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:6144:129024:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297414 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:9216:129024:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297419 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:12288:129024:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297425 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:0:132096:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297430 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:3072:132096:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297436 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:6144:132096:3072:3072:0 was dropped because of time out (5619ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297441 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:9216:132096:3072:3072:0 was dropped because of time out (5618ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

Jul 27 17:58:03 wsd-00014-34881 2022-07-27 15:58:03.297446 +0000 [ docbroker_611 ] WRN ToClient-666f: Tracker tileID 0:12288:132096:3072:3072:0 was dropped because of time out (5618ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2000

2

My number one guess is the issue stems from your server specs.

What are your actual server specs? What kind of hardware?

  • CPU type
    • arm64 or x86-64
    • are you using a Raspberry Pi? If so, it supplies only the bare minimum specs as of Model 4.
  • How much RAM
    • If less than 4gb ram by itself, that is horrible.
  • How fast is your network speed?
    • If only xx mb/s of speed, you are hurting.
    • Please do not run your server over wifi. Very very slow.
    • Upgrade your network to wired gigabit if you can. Will greatly increase speeds.
    • External networking speeds will be hampered by your actual ISP speeds.
  • What kind of disks?
    • Spinning sata is fair
    • USB 2.0 external spinning drive garbage
    • Micro-SD card garbage
    • eMMC is not good
    • USB 3.0 external drive is fair for light usage
    • nvme Good!
    • SSD Good!
  • How many users?
  • Are you using one of the office suites?
    • Collabora CODE, OnlyOffice, etc?
    • If so, less than an additional two cores and additional 4gb ram is horrible.
  • Are you running other services on the same machine?
    • Matrix, Jellyfin, Jitsi, ?
    • If yes, you’ll need even more ram, etc.
3

Have you found an Solution?

Have the same Problem that collabora loads slowly.

Installed on the system, no docker Setup.

System:

  • Debian 11
  • CPU: AMD Ryzen 5 3600 6-Core
  • x86
  • 64 GB RAM
  • RAM used: 20 GB.
livesystem-debian coolwsd[3889969]: wsd-3889969-3895779 2023-04-19 07:09:12.713323 +0200 [ docbroker_001 ] WRN  ToClient-002: Tracker tileID 0:0:5485:3291:1097:1097:1 was dropped because of time out (8520ms). Tileprocessed message did not arrive in time.| wsd/ClientSession.cpp:2233