Comment - FBXL Lotide

Comment on Issue: The limits of the cloud?

And it’s reproducible: files newly added to certain directories cause the timeout error. Older files already present in precisely these directories do not cause the error, even when reused in a post.

Just a wild guess: new files are being fetched by all receivers, old files might already be cached and will not be fetched in the same extend as new ones.

original

Sort:hotnew top

pepecyb@hub.hubzilla.hu@hub.hubzilla.hu ⁨2⁩ ⁨weeks⁩ ago
That also seems rather unlikely, although the thought had crossed my mind too.

Example:

I upload the image A.png (a completely new image) to the “Artikelbilder” folder and embed it in a post: after a short while, the hub freezes and displays the error message in the log.

After rebooting, I delete the post and the image.

Then I upload the image A.png again to a different directory and use it in a post: no error occurs.

I upload a completely new image, B.png, to a different directory and use it in a post: no error occurs.

I upload the image B.png to “Artikelbilder” and use it in a post: after a short while, the hub freezes and displays the error message in the log.

Reboot, delete…

I move the image B.png from the other directory to “Artikelbilder” and use it for a post: after a short while, the hub freezes and displays the error message in the log.

The only thing that might explain this is that the issue does not occur with older images already present in the critical directories.
original
- mario@hub.somaton.com ⁨2⁩ ⁨weeks⁩ ago
  @Der Pepe (Hubzilla) ⁂ is there a difference/correlation in how often the image is accessed (server access log) compared between the different scenarios?
  original
  - pepecyb@hub.hubzilla.hu@hub.hubzilla.hu ⁨2⁩ ⁨weeks⁩ ago
    Several tests (in which the hubs consistently froze) showed no significant differences in the number of times images were accessed.
    
    Nor did the method of referencing in the source code (i.e. <HUB>/photos/<HASH_FILENAME> or <HUB>/cloud/<CHANNEL_NAME>/<REAL_FILENAME>) make any difference. New images from the two problematic subdirectories caused the system to freeze, whilst images from other directories did not. I’ve now simply stopped using those two directories for new uploads… but that's obviously just treating the symptoms.
    original
    mario@hub.somaton.com ⁨2⁩ ⁨weeks⁩ ago
    @Der Pepe (Hubzilla) ⁂ do you have slow log enabled for your DB backend? Maybe it reveals something :thinking_face:
    
    Performance differences when accessing new vs old files does not make much sense to me though :person_shrugging:
    original
    -> View More Comments
  - pepecyb@hub.hubzilla.hu@hub.hubzilla.hu ⁨2⁩ ⁨weeks⁩ ago
    I’m going to give that a proper go today to see if I can spot any differences.
    I’ll get back to you as soon as I have the results.
    original