Plan with lamp, more pictures, need to pay attention to what?
The first requirement is to be as stable as possible and then to ask for higher efficiency
Reply to discussion (solution)
Is the image placed on the server's hard drive or in the MySQL database? Is there something different about these two?
If you use a picture server alone, use Nginx as a Web server, whether it is more wasteful
If the picture is large, and frequently used, it is recommended to store a separate server, as for the MySQL binary storage, or hard disk storage, specific to see your business needs.
The storage database is certainly slower than the direct storage drive
If only the general Web site to install the image server Nginx alone to engage in a domain name.
If you want a professional point of recommendation rack a ZIMG server
If the picture is large, and frequently used, it is recommended to store a separate server, as for the MySQL binary storage, or hard disk storage, specific to see your business needs.
What's different about their business?
I think that, if the picture is many, and the logic of the query is more complex, suitable for the database, and if the logic of the query is relatively simple, directly on the hard disk, so performance will be better. Is there any other consideration?
Thanks for pointing.
The storage database is certainly slower than the direct storage drive
If only the general Web site to install the image server Nginx alone to engage in a domain name.
If you want a professional point of recommendation rack a ZIMG server
The number of pictures is about tens of thousands of, not very large, the largest is 3 m, user access is not very frequent, but requires a page to open 10 pictures, open the speed can not be too slow
If you use only one server, put the picture on disk, such a scheme is sufficient
Thank you!
The storage database is certainly slower than the direct storage drive
If only the general Web site to install the image server Nginx alone to engage in a domain name.
If you want a professional point of recommendation rack a ZIMG server
The number of pictures is about tens of thousands of, not very large, the largest is 3 m, user access is not very frequent, but requires a page to open 10 pictures, open the speed can not be too slow
If you use only one server, put the picture on disk, such a scheme is sufficient
Thank you!
It must be enough for your description.
One page opens 10 images and there's 3 m. This has to be used JS to speed up the first screen of the picture scroll bar scroll down after opening the following diagram
The storage database is certainly slower than the direct storage drive
If only the general Web site to install the image server Nginx alone to engage in a domain name.
If you want a professional point of recommendation rack a ZIMG server
The number of pictures is about tens of thousands of, not very large, the largest is 3 m, user access is not very frequent, but requires a page to open 10 pictures, open the speed can not be too slow
If you use only one server, put the picture on disk, such a scheme is sufficient
Thank you!
It must be enough for your description.
One page opens 10 images and there's 3 m. This has to be used JS to speed up the first screen of the picture scroll bar scroll down after opening the following diagram
My approach is to store images directly under the file for easy file management.
One page 10 pictures not much, how to do it. The picture is placed on the hard drive, and the path is saved in the database.
The storage database is certainly slower than the direct storage drive
If only the general Web site to install the image server Nginx alone to engage in a domain name.
If you want a professional point of recommendation rack a ZIMG server
The number of pictures is about tens of thousands of, not very large, the largest is 3 m, user access is not very frequent, but requires a page to open 10 pictures, open the speed can not be too slow
If you use only one server, put the picture on disk, such a scheme is sufficient
Thank you!
It must be enough for your description.
One page opens 10 images and there's 3 m. This has to be used JS to speed up the first screen of the picture scroll bar scroll down after opening the following diagram
OK, see, then I'll find a way to use JS solution.
It's not too high a technical requirement to visually
The storage database is certainly slower than the direct storage drive
If only the general Web site to install the image server Nginx alone to engage in a domain name.
If you want a professional point of recommendation rack a ZIMG server
The number of pictures is about tens of thousands of, not very large, the largest is 3 m, user access is not very frequent, but requires a page to open 10 pictures, open the speed can not be too slow
If you use only one server, put the picture on disk, such a scheme is sufficient
Thank you!
It must be enough for your description.
One page opens 10 images and there's 3 m. This has to be used JS to speed up the first screen of the picture scroll bar scroll down after opening the following diagram
My approach is to store images directly under the file for easy file management.
OK, thank you, I try to save the icon directly how the effect
One page 10 pictures not much, how to do it. The picture is placed on the hard drive, and the path is saved in the database.
Yes, thanks a very much!