blocks|key|1760399|text|在iOS上，任何数量的映像都不是真正的问题，因为有一些高级缓存系统可以处理映像的重用。而且，iOS的渲染系统非常棒，所以您不必担心它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1760400|虽然它当然有可能为精灵系统编程，但我不会建议你这么做。这种方法主要用于Web+(因为每个图像都必须带有新的请求*注意HTTP/2不再正确)，而且显然也用于游戏开发(因为绑定纹理调用越少，越好)。|offset|length|1760401|还有一个很好的例子说明为什么不使用精灵--如果您正在开发Watch应用程序，并且您想做动画，您可以通过flipboard样式的图像(名为1.png+-100.png的图像序列)来完成，而不是使用大型的图像地图集。虽然人们会猜测为什么他们会这样做(我猜是因为它在内部工作得有多好%2B蓝牙的吞吐量)，但很明显，它也是苹果的首选，因此我们应该遵循。|1760402|对于iOS，有一些陷阱您应该知道：|1760403|从网络加载的任何图像都不应该加载在主线程上，对于屏幕加载时没有显示的图像也是如此(+UITableViewCell中的图像是一个很好的例子，因为当图像滚动时，如果图像很大，就可以看到迷你冻结)。|unordered-list-item|1760404|如果您有很多层，那么使用alpha通道!=+1的图像会严重降低性能(但通常是不可避免的)。|1760405|使用UIColor.colorWithPatternImage()创建的背景图像应该谨慎使用，因为这种方法被认为是有问题的(这里的细节)|style|CODE|1760406|现在，关于映像的异步加载，我建议您查看以下库：|1760407|哈内克(Obj，斯威夫特)|1760408|SDWebImage+(Obj)|1760409|它们都很棒，所以这确实是首选问题(我更喜欢Haneke+)，但是它们允许您在不同的线程上下载图像，无论是从Web还是从您的包中下载。它们还为UIImageView提供了扩展，允许您使用一行函数轻松加载所有图像。|1760410|希望能帮上忙！|1760411|entityMap|0|LINK|mutability|MUTABLE|url|http://qnimate.com/what-is-multiplexing-in-http2/|1|https://stackoverflow.com/questions/10043077/ios-using-a-pattern-image-as-a-background-memory-leak|2|https://github.com/Haneke/Haneke|3|https://github.com/Haneke/HanekeSwift|4|https://github.com/rs/SDWebImage^0|0|1M|A|0|0|0|0|0|0|2|V|1Q|5|1|0|0|4|3|2|8|4|3|0|C|3|4|0|0|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1J|8|@]|9|@$D|1K|E|1L|1|1M]]|A|$]]|$1|F|3|G|5|6|7|1N|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1O|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1P|8|@]|9|@]|A|$]]|$1|M|3|N|5|L|7|1Q|8|@]|9|@]|A|$]]|$1|O|3|P|5|L|7|1R|8|@$D|1S|E|1T|Q|R]]|9|@$D|1U|E|1V|1|1W]]|A|$]]|$1|S|3|T|5|6|7|1X|8|@]|9|@]|A|$]]|$1|U|3|V|5|L|7|1Y|8|@]|9|@$D|1Z|E|20|1|21]|$D|22|E|23|1|24]]|A|$]]|$1|W|3|X|5|L|7|25|8|@]|9|@$D|26|E|27|1|28]]|A|$]]|$1|Y|3|Z|5|6|7|29|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|2A|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|2B|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]|1A|$5|15|16|17|A|$18|1B]]|1C|$5|15|16|17|A|$18|1D]]|1E|$5|15|16|17|A|$18|1F]]|1G|$5|15|16|17|A|$18|1H]]]]

[any number] of images is not really a problem on iOS since there are advanced caching systems in place that take care of reuse of the images. Also the rendering system of iOS is quite great so you don't have to worry about it. 

While it is certainly possible to program system for sprites, I would not advice you to do it. This method is primarily used in Web Development (because each image has to be served with new request *note <a href="http://qnimate.com/what-is-multiplexing-in-http2/" rel="nofollow noreferrer">no longer true with HTTP/2</a>) and also obviously for game development (because the less bind texture calls you have, the better). 

There is one more good example for why not to use sprites - if you are developing Watch application and you want to do animation, you do it through flipboard style images (sequence of images named 1.png - 100.png), and not by using large atlas of images. While it would be guessing as why did they decide to do it that way (my guess would be because of how good it works internally + throughput of the bluetooth), it is obvious that it is also preferred choice of Apple and so we should follow.

For iOS, there are some pitfalls that you should know:

<ul>
<li>Any image loaded from the Web should not be loaded on main thread, the same really goes with every image that is not present at the load of the screen (images in UITableViewCell are great example, because you can see mini-freezes if the images are large as you are scrolling through)</li>
<li>If you have many layers, images with alpha channel != 1 decrease performance heavily (but are often unavoidable)</li>
<li>Background image created with <code>UIColor.colorWithPatternImage()</code> should be used with caution, as this method is considered problematic (<a href="https://stackoverflow.com/questions/10043077/ios-using-a-pattern-image-as-a-background-memory-leak">details here</a>)</li>
</ul>

Now as for asynchronous loading of the images, I suggest you take a look at following libraries:

<ul>
<li>Haneke (<a href="https://github.com/Haneke/Haneke" rel="nofollow noreferrer">Obj-C</a>, <a href="https://github.com/Haneke/HanekeSwift" rel="nofollow noreferrer">Swift</a>)</li>
<li>SDWebImage (<a href="https://github.com/rs/SDWebImage" rel="nofollow noreferrer">Obj-C</a>)</li>
</ul>

Both of them are great so it is really matter of preference (I like Haneke better), but they allow you to download images on different threads, be it from Web or from your bundle. They also have extensions for UIImageView which allows you to use 1-line function to load all images easily.

Hope it helps!

blocks|key|1760440|text|如果这一点算上的话，iOS+9就会出现;)它被称为随需应变资源(+On+)，它允许你用苹果存储内容，并在需要的时候下载内容，等等。这对于游戏应用程序来说是很棒的，也是它们在WWDC中的一个例子。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1760441|看看这里：指南/指南|offset|length|1760442|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.apple.com/library/prerelease/ios/documentation/FileManagement/Conceptual/On_Demand_Resources_Guide/^0|0|5|5|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

There will be in iOS 9 if that counts ;) It's called On Demand Resources and lets you store content with Apple and download the content when it's needed for a level, etc. It'll be great for game apps and is what they used as an example at WWDC.

Check it out here: <a href="https://developer.apple.com/library/prerelease/ios/documentation/FileManagement/Conceptual/On_Demand_Resources_Guide/" rel="nofollow">https://developer.apple.com/library/prerelease/ios/documentation/FileManagement/Conceptual/On_Demand_Resources_Guide/</a>

My app <code>UIKit</code> stores something like 100 <code>(100x100) jpeg</code> files, that suppose to be used as "pattern image". the average size for each image is sometimes like <code>20~40 kb</code>.

I'm cocos2d-x developer as well. In cocos environment i'm using <code>plist</code> to "bound" each image and than cut it via <code>plist</code>. This is great performance and size saver, but as far as I know its not possible on <code>UIKit</code>.

So my question is this, Is there a better way to store/pull this images to improve disk capacity and increase performance, other than drag and drop the files into XCode and use it as usual?

IOS - Best practice to handle large number of images (Performance + Size on disk)

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我的应用程序UIKit存储大约100个(100x100) jpeg文件，这些文件应该用作“模式图像”。每个图像的平均大小有时类似于20~40 kb。我也是cocos2d-x开发人员。在cocos环境中，我使用plist“绑定”每个图像，而不是通过plist对其进行切割。这是一个很好的性能和大小保护程序，但据我所知，这在...

问IOS -处理大量图像的最佳实践(性能+磁盘上的大小)
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问IOS -处理大量图像的最佳实践(性能+磁盘上的大小)EN