Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can it be faster than FastEasyMapping? MJExtension take 15 seconds and FastEasyMapping take 8 seconds #197

Open
steve21124 opened this issue Sep 8, 2015 · 0 comments
Milestone

Comments

@steve21124
Copy link

using current MJExtension example. it take about 15 seconds to process 100 rows of json data. Using FastEasyMapping, it only take about 8 seconds. I am looking for solution which will take about 4 seconds.
https://gist.github.com/steve21124/0cd62b06047d7a98a6ce

and this the json data
https://www.dropbox.com/s/zpxjl5wsjfpe2sm/JSONData.json.zip?dl=0

do you know possible solution?

thanks for the great library

@steve21124 steve21124 changed the title Can it be faster than FastEasyMapping? Can it be faster than FastEasyMapping? MJExtension take 15 seconds and FastEasyMapping take 8 seconds Sep 8, 2015
@wolfcon wolfcon added this to the 4.0.0 milestone Nov 23, 2021
wolfcon added a commit that referenced this issue Dec 23, 2021
  - `String to Data` case
  - `AttributedString to String` case
Remove unnecessary ivar of cache class.
Boost large properties with small amount dictionary. #197
wolfcon added a commit that referenced this issue Dec 23, 2021
  - `String to Data` case
  - `AttributedString to String` case
Remove unnecessary ivar of cache class.
Boost large properties with small amount dictionary. #197
wolfcon added a commit that referenced this issue Jan 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants