-
Notifications
You must be signed in to change notification settings - Fork 364
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
Execute file size is too big, can sonic be optimized when compile? #574
Comments
Ok, I will try it. First investigate where the binary comes from. If you already have stats on it, it will help a lot |
Those are my project execute files, two methods for json parsing, Windows 10, CPU Intel Core i7. method1: json parse, execute file size: 48M
method 2: sonic parse, execute file size: 97M
|
Can you try to use older version (<1.10) and give size? If it is still a lot, I doubt that the main cause it doesn't come from C asm files. |
@AsterDY |
ok,It seem native codes need to be embeded on demands. Let me try |
Hi there, |
Also, the compilation time is x2 for v1.10, on 1.9.2 it's two times faster. |
Might be useful #561 (comment) |
Seem it is due to v1.10 imported iasm as basic assembler (#393), which is used to reslove #489 meanwhile improve C-Go intercall performance. At present, no better solution for this. cc @chenzhuoyu |
这个会优化吗? |
@rts-gordon I think it's done. |
Hi there,
Sonic is a great json library, high performance and very easy to use, thanks for your work.
But the execute file size is double, it is can‘t acceptable in my scenario. Can sonic be optimized when compile? for example: only compile source code for CPU/OS arch currently in use, maybe this will reduce execute file size.
Thank you.
The text was updated successfully, but these errors were encountered: