@Der Pepe (Hubzilla) ⁂ is there a difference/correlation in how often the image is accessed (server access log) compared between the different scenarios?
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.
Good idea to enable slow log for another series of tests. I’ll do that.
Performance differences when accessing new vs old files does not make much sense to me though
That’s exactly why I’m confused. The only thought I had was whether it might somehow be down to the number of entries in the directory. However, the two directories do differ in the number of entries. What they have in common is the rather large total size (MB). I’ve no idea at the moment.
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.
Performance differences when accessing new vs old files does not make much sense to me though :person_shrugging:
That’s exactly why I’m confused. The only thought I had was whether it might somehow be down to the number of entries in the directory. However, the two directories do differ in the number of entries. What they have in common is the rather large total size (MB). I’ve no idea at the moment.