New geo files are not optimized

[HappDev]

Good afternoon, developers.

The new geo files you’ve added contain a lot of unnecessary information, and sometimes it doesn't match the appropriate categories. This results in increased memory usage. iOS, for example, does not allow using more than 50MB of memory. This leads to either XRay running slowly (at the peak of allowed memory) or the app being terminated by the system due to exceeding resource limits.

https://youtu.be/07O_7_9Ic_E

[iambabyninja]

Good afternoon, dear members of our community!

Specifically, we know for certain that in the current versions of iOS, we have the following memory limitations:

Provider	Limit (MiB)
packet tunnel	50
app proxy	15
filter control	50
filter data	50
DNS proxy	15
app push	24

In our case, Xray is a network process limited to 50MB. It reads geo files and then operates with the read content.

Unfortunately, with the current implementation of geofiles in our core, where all categories are in one large file, we often encounter the inability to even simply start the tunnel on an Apple device.
In particular, with the new geolocation files that we received from our partners, the file sizes have become significantly larger, which means that we cannot load them into memory.

A simple example (Loyalsoldier geosite):

None of the first four categories, if set in the routing rules, will allow the tunnel to start.

This also applies to geo files with CIDR (Loyalsoldier geoip)
Simple example:

@RPRX , considering the memory constraints, perhaps we should explore refactoring the geofile handling code. We could draw inspiration from neighboring teams and implement a system that utilizes multiple smaller files instead of one monolithic file. This approach could effectively resolve the memory issues on Apple devices. What you think about this?

[sudoloveme]

还有如果你用iOS或iPadOS你不可能用geosite:cn，由于RAM消耗超过50MB，因此在iOS上使用VPN的限制为50MB