blocks|key|4769834|text|存储完整文件，然后根据需要生成其他大小的文件并缓存它们；页面处理在第一个请求时会稍微减慢，但随后的所有请求都将使用缓存的版本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4769835|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Store the full then generate the other sizes as needed and cache them; page processing will be slowed down a little on the first request but then the cached version would be used for all subsequent requests.

blocks|key|4769852|text|既然你认为存储的图像会很多，请求也不会很多，我会选择动态调整大小的解决方案，因为听起来你已经知道存储空间将是更大的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4769853|如果你想变得更花哨，你可以设置一个MRU+(最近使用的)缓存n-最常请求的调整大小的图像，但同样，如果请求数量很少，这可能会被夸大-但仍然可能是一个有趣的项目！;)|4769854|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Since you think there will be many images stored and not very many requests, I'd go with the resize-on-the-fly solution, since it sounds like you already know storage space will be the bigger issue.

If you wanted to get fancy, you could set up an MRU (most recently used) cache of the n-most commonly requested resized images, but again, if low number of requests this would probably be overkill - but still might be a fun project! ;)

blocks|key|1080432|text|与标准HTTP动词相比，REST和用法的关键点之一是它支持缓存；我认为这将支持动态调整大小的意图。不过，这实际上是一个存储空间与请求时间计算之间的权衡问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1080433|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

One of the key points of REST and the usage over the standard HTTP verbs is that it supports caching; I think that would support the intent to do dynamic resizing. It's really a question of tradeoff of storage space vs. request-time computation, though.

blocks|key|1080455|text|如果系统负载不是问题(假设是低容量的intranet应用程序)，我会选择存储完整大小的图像，并在运行时对其进行缩放。这样，如果您需要其他大小，您将不需要替换所有的图像。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1080456|但正如您上面所说的，了解折衷并对系统负载、磁盘空间、需求更改的可能性等做出一些良好的估计。|1080457|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If system load is not an issue (assuming a low volume intranet app) I would go with storing the full size image and scale it at runtime. That way if you ever need other sizes, you won't need to replace all of your images.

But as you stated above, understand the trade offs and make some good estimations of systems load, disk space, likelihood of requirements changing, etc.

blocks|key|2697069|text|另一种选择是维护调整大小的图像的缓存。提供可用的服务。如果它们不可用，请创建新的。删除一段时间内未被请求的镜像。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2697070|这将是CPU和存储问题之间的折衷。|2697071|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Another option is to maintain a cache of resized images. Serve up the ones that are available. Create new ones if they are not available. Delete images that have not been requested for a while.

This will be a compromise between the CPU and storage issues.

blocks|key|4770017|text|您自己回答了这个问题，这是CPU和空间之间的权衡。你知道每条路径的成本，只要问问你自己，哪种资源对你来说更昂贵。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4770018|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You answered the question yourself, it's a CPU-Space tradeoff.
You know the costs of each path, just ask yourself, which resource is more costly for you.

I'm working on a CMS and I'm trying to figure out the common practice for doing a REST style image request. I have three sizes, small, medium, and full. My thought is to store only the full and write a function that will resize on each page request. This has obvious cpu costs. The other end is that I could store all three sizes and only calculate on upload, this seems to waste space.

My environment is an intranet, so relatively low requests and a high number of images stored. Thoughts?

Note: I realize I don't have to really worry too much since it's intranet and either solution will work, just wondering which would be preferred for knowledge sake.

Store multiple sizes of an image or just store the main and resize?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在做一个CMS，我正在尝试找出做REST样式图像请求的常见做法。我有三种尺码，小号、中号和大号。我的想法是只存储完整的，并编写一个函数，该函数将根据每个页面请求调整大小。这有明显的cpu开销。另一端是，我可以存储所有三个大小，并且只在上传时计算，这似乎是浪费空间。我的环境是一个内部网，因此相对较低的请求和大量的图像...

问存储多个大小的图像，还是只存储主图像并调整大小？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问存储多个大小的图像，还是只存储主图像并调整大小？EN