MongoDBGridFSstoremultiplesizesofimageoruseontheflyresizing

4  

Resizing on the fly will result in far more CPU load on your server than resizing to a variety of sizes once, and storing the results. On the other hand, resizing ahead of time may result in a larger set of data to be stored in GridFS. In other words, it's a tradeoff.

动态调整大小会导致服务器上的CPU负载大大超过调整大小一次,并存储结果。另一方面,提前调整大小可能会导致更大的数据集存储在GridFS中。换句话说,这是一个权衡。

You could consider a hybrid approach, where you resize on the fly but save the results back to GridFS so that you don't need to resize any one image to a given size more than once.

您可以考虑使用混合方法,在其中您可以动态调整大小但将结果保存回GridFS,这样您就不需要将任何一个图像大小调整为给定大小多次。

You should also know that HTML and CSS allow various options for controlling the displayed size of an image. For example:

您还应该知道HTML和CSS允许使用各种选项来控制图像的显示大小。例如:

Will result in an image scaled proportionally to 50 pixels wide (in most modern browsers, at any rate). You can also use the width and max-width CSS properties to control image size.

将导致图像按比例缩放到50像素宽(在大多数现代浏览器中,无论如何)。您还可以使用宽度和最大宽度CSS属性来控制图像大小。

For myself, and knowing nothing about the volume or file size of the images you'll be storing, I'd probably resize when images are added -- in other words, take the page speed and CPU load hit once -- and then serve the various sizes out of GridFS, using max-width to control the on-screen size if a slightly different size is required in one particular case.

对于我自己,并且对要存储的图像的音量或文件大小一无所知,我可能会在添加图像时调整大小 - 换句话说,将页面速度和CPU负载调整一次 - 然后服务GridFS的各种尺寸,如果在一个特定情况下需要稍微不同的尺寸,则使用max-width来控制屏幕尺寸。