By ETS-Consulting on Thursday, 22 December 2016
Posted in General Issues
Replies 6
Likes 0
Views 570
Votes 0
hi StackIdeas,

In Komento there is an issue to be improved. If any comment item contains image attachments there is no thumbnails generated to be displayed in comment item. All images are fetched as original.

So there are two performance problems with this implementation:

- images are always original - users download megabytes of data - bad for the users and Google punishes it. See my screenshot.
- image path is not direct link to image file - what is maybe ok for non-image attachment but very unperformant for images. Many hosts are using components like NGINX to server static content. But having images crypted this way those are not recognised as images. This content also can not be cached by browser.

Could you please address this issue in the new version of Komento? I realised this problem just right now when my users started to complain when trying to open article having comments with many image attachments.

I also asked you many times to add a feature to automatically scale all images uploaded by users as attachment. I have implemented this on my own in Komento (just a few line of code). I could not imagine how slow would be downloading the real original files every time users access the article.

Please do not ignore my request for improvement.

best regards
Martin

- images are always original - users download megabytes of data - bad for the users and Google punishes it. See my screenshot.

We try to not resize anything right now to reduce the number of support requests. If we ever implement this, someone else is going to start posting a new issue that Komento is taking up a lot of disk space generating a lot of thumbnail files.


- image path is not direct link to image file - what is maybe ok for non-image attachment but very unperformant for images. Many hosts are using components like NGINX to server static content. But having images crypted this way those are not recognised as images. This content also can not be cached by browser

Thanks for your input on this and we'll consider this. The only reason that images are served via PHP over direct file linkage is to avoid people finding these files but looking at the way it is right now, those files are already hashed and it's almost impossible to guess them.
·
Thursday, 22 December 2016 23:28
·
0 Likes
·
0 Votes
·
0 Comments
·
hi Mark,

>> We try to not resize anything right now to reduce the number of support requests. If we ever implement this, someone else is going to start posting a new issue that Komento is taking up a lot of disk space generating a lot of thumbnail files.

please ... really .. did you read my arguments ?

- users are complaining
- Google points is out as urgent issue to be fixed
- server storage is very high.


what do you mean with thumbnails consumes storage ?????

currently if the user upload a 4MB jpg file it costs a lot of storage and website is very bad performance. If Komento would scale down the image to let say 1000px + thumbnail it would cost 100kb + 10kb. So I dont really understand what do you mean thumbnails costs storage.

I do not really understand why do you reject constantly important improvements requests?

I really love your products but I am really tired trying to argumenting you the problems in those ...

Martin
·
Thursday, 22 December 2016 23:50
·
0 Likes
·
0 Votes
·
0 Comments
·
We will consider your request
·
Friday, 23 December 2016 00:10
·
0 Likes
·
0 Votes
·
0 Comments
·
hi Mark,

I have checked today which php script generates the higher load of my server (CPU) and one of them is exactly the:

/index.php?option=com_komento&controller=file&task=download

even if I still do not have too many comments with attachments. My server is quite strong (4CPUs, 32GBM RAM)

I am going to modify locally kommento to point directly the image files instead of involving CPU for that. Please consider to make this an option in kommento.

thanks in advance
Martin
·
Saturday, 21 January 2017 20:27
·
0 Likes
·
0 Votes
·
0 Comments
·
All the download method does is to read the file from the server and push it back to the user and nothing else is being done so I have absolutely no idea why is the CPU load is affected.

The reason that this is served through PHP is to avoid users with unauthorized access to be able to view the file. Imagine if a person doesn't have access to the comments on the page and somehow gotten the link to the file directly, then the person would be able to view those items.

In your site scenario, it makes perfect sense if everything is public but some sites has restrictions on their comments and only want to allow registered users or certain user groups to view the comments. This would prevent direct hot linking to those attachments.
·
Saturday, 21 January 2017 23:55
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post