Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
i do not have an issue with disk space and with my web app only 30 images will be loaded at once, issue is there is a 3 second ajax for these images so they are either.
A. mysql query every 3 seconds per image. (per viewer)
B. Use Uploaded Photos.
At the moment I am assuming an uploaded photo is the best but I am not the pro at these things so I wanted a second opinion. Thanks.
I’m sorry, your question is not very clear.
If you’re worried about multiple MySQL queries, that is not an issue, assuming your are not running mulitple queries around the clock.
On my web apps, a single page load will query the database 10 to 50 times. But that is nothing for a good host.
Edit: generally speaking, it’s faster to store the image files on the webserver, rather than storing them as blobs in the database; they will be delivered by the server which is optimized for it. Instead store the image filenames in your database and reference them that way.