High memory consumption with numerous data points

[RaistlinKong]

280MB memory consumption with nearly 100 data input, a bit more data will cause application terminated for memory pressure.

[FrederickGeek8]

When I have 131 data points by memory is only 111.7 MB. Thats still high but not 280 MB high...

Something that I've been doing for large point sets is to reduce their size with the function outlined here.
I then apply:

// Reduce sizes
if([graphs count] > 150){
       [self.graphs removeOddElements];
}
// Check again because I'm too lazy to write a for loop
if([graphs count] > 150){
        [self.graphs removeOddElements];
}

[Boris-Em]

Hi @RaistlinKong and @FrederickGeek8,
Are you guys using the build on the feature branch?
I still have to run some test but in theory, it's supposed to be better performance wise.

[RaistlinKong]

Hi @Boris-Em and @FrederickGeek8
I am using the master branch, it do cost 208MB memory with near 106 data, memory doubled may because the application running on iOS7 64bit and your one running on 32bit. Something fundamental needed to change to save memory further.

[FrederickGeek8]

I'm using the master branch for the sake of production development. (For reference I'm running iOS 8; iPhone 5s)

[Boris-Em]

Hi @RaistlinKong & @FrederickGeek8,
I had time to run some tests this week end. I used 106 points on an iPhone 4:

• about 120MB with the Master branch (similar to what @FrederickGeek8 is experiencing)
• about 6MB with the Feature branch

It's a big improvement.
The feature branch is pretty stable right now, which means that I'm hoping to merge it to the Master branch soon.

[RaistlinKong]

Hi @Boris-Em :

That's really a big improvement! 👍

[FrederickGeek8]

I look forward to it!

[chinedufn]

Has this been resolved?