Comment 8 for bug 2048103

@Brian Rosmaita,

I have tried to populate all the properties using the Image REST API without involving Horizon. Each property can be up to 64KB in size. By default, each image can have a maximum of 128 properties, allowing for a total of 8MB of property data per image. With the default configuration, each user can have 128 images, allowing for nearly 1GB of junk data to be filled per user. If the default configuration is modified to allow for larger images or a user has multiple projects, there is a possibility for even more junk data to be filled by a single user.

Furthermore, I have observed that accessing image details becomes very slow when we populate the properties up to the 8MB limit. I simulated 50 threads on a single machine, using the same user's cookies to access image details. It was found that requests from other users were significantly delayed, especially when trying to access the images through Horizon. It was almost impossible for other users to access the images successfully.