You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've run performance tests on YaLinqo, Ginq and Pinq. Whenever I use property access syntax, performance of Ginq queries drops 2-5 times. See gist with performance results (results from YaLinqo master branch). You should cache functions or something. Using "string lambdas" in YaLinqo, which rely on create_function, does decrease performance, but not so significantly (since I've added caching, inner queries stopped killing performance too).
Just curious, is using explicit iterator classes instead of generators a deliberate design decision, or do you just aim for compatibility with older PHP versions?
P. S. Thanks for competition. Ginq and Pinq forced me to finally update my library: add missing methods, improve performance, add integration with continuous integration and code quality tools, put reference documentation online etc. 😀
The text was updated successfully, but these errors were encountered:
Your competitor here. 😀
I've run performance tests on YaLinqo, Ginq and Pinq. Whenever I use property access syntax, performance of Ginq queries drops 2-5 times. See gist with performance results (results from YaLinqo master branch). You should cache functions or something. Using "string lambdas" in YaLinqo, which rely on
create_function
, does decrease performance, but not so significantly (since I've added caching, inner queries stopped killing performance too).Just curious, is using explicit iterator classes instead of generators a deliberate design decision, or do you just aim for compatibility with older PHP versions?
P. S. Thanks for competition. Ginq and Pinq forced me to finally update my library: add missing methods, improve performance, add integration with continuous integration and code quality tools, put reference documentation online etc. 😀
The text was updated successfully, but these errors were encountered: