-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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
Performance issue, result set processing #1672
Comments
I just thought a bit more, this issue comes from the size of the result set from mysql. As the sample provided above, the result set is And I tried several different size of result set:
Seems it's not good to handle queries with big size of result using typeorm. What do you guys suggest to do with this use case? Is it possible to enhance the performance of this case? |
thanks for the report. I'll try to fix this issue quickly and will return back to you with results. |
Optimized and released in Results for 100000 rows hydration on my local machine: select using raw sql query (node-mysql): 197.424ms // nothing can be faster then this There is still room for optimization but all other places aren't as serious as this one fixed. |
That's awesome. Thank you for your work! |
thanks for the report! |
* master: skipping test for now to make CI working version bump fixed bug with partial selections via find options version bump fixed issue with find options accepting keys as expressions Update parameter name to stay consistent Update mongodb.md add unit test for issue 1685 Feature to provide custom migration table name add tests for issue fix connection url parsing fixing #1672 Fix #1656 check if entity file already exists # Conflicts: # CHANGELOG.md # package.json # src/decorator/transaction/Transaction.ts # src/migration/MigrationExecutor.ts # src/query-builder/QueryBuilder.ts # src/query-builder/transformer/RawSqlResultsToEntityTransformer.ts
Issue type:
[x] question
[ ] bug report
[ ] feature request
[ ] documentation issue
Database system/driver:
[ ]
cordova
[ ]
mongodb
[ ]
mssql
[x]
mysql
/mariadb
[ ]
oracle
[ ]
postgres
[ ]
sqlite
[ ]
sqljs
[ ]
websql
TypeORM version:
[ ]
latest
[ ]
@next
[x]
0.1.13
(or put your version here)Complete codes can be found here: gist
Simple mysql search:
Run the same sql in mysql directly:
Time consumption is
25 : 0.2
. Seems not good.Result of
node --prof build/app.js
&node --prof-process isolate-0x102802400-v8.log
:Is there anything I made wrong? Please help.
The text was updated successfully, but these errors were encountered: