Replies: 1 comment
-
Bulk insert is optimized for inserting / updating a LOT of values, as soon as possible. Note that it is not safe to use a single bulk insert concurrently. I don't think that this is a good scenario for you needs. However, this is likely better: The idea is to reduce overall costs in network transfer / disk I/O. You have a small queue that you'll wait to fill until a certain size / time reached. Then you send it to the server (basically, Session + SaveChanges()). You'll report success to everything in the batch when you are done with the batch. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
We potentially have to handle many many thousands of inserts over a short time period in a large web-based app. Is there any way to add the inserts/updates to a queue and place them on a background thread to bulk insert them later?
We are measured on the response time from the users device and the slowest call is the insert/update, if we queue this it will reduce the perceived response time.
Beta Was this translation helpful? Give feedback.
All reactions