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
Copy file name to clipboardExpand all lines: docs/index.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,7 +125,7 @@ context.BulkMerge(customers,
125
125
<div class="row">
126
126
<div class="col-lg-5 left wow slideInLeft">
127
127
<p>
128
-
Make your save operations <span class="text-z">10 to 50 times</span> faster.
128
+
Perform save operations <span class="text-z">10 to 50 times</span> faster.
129
129
</p>
130
130
<p>
131
131
Support all major providers:
@@ -236,7 +236,7 @@ context.BulkMerge(customers,
236
236
<h2 class="wow slideInUp">Bulk SaveChanges</h2>
237
237
<div class="row">
238
238
<div class="col-lg-5 wow slideInLeft">
239
-
<p class="feature-tagline">Add 4 letters <span class="text-z">Bulk</span> to make your application <span class="text-z">10-50 times</span> faster and more responsive.</p>
239
+
<p class="feature-tagline">Add the 4 letters word <span class="text-z">Bulk</span> to make your application <span class="text-z">10-50 times</span> faster and more responsive.</p>
Copy file name to clipboardExpand all lines: docs/pages/api/bulk-delete.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,9 +21,9 @@ context.BulkDelete(customers, options => options.ColumnPrimaryKeyExpression = cu
21
21
22
22
Despite the `ChangeTracker` being outstanding to track what's modified, it lacks in term of scalability and flexibility.
23
23
24
-
`SaveChanges`require one database round-trip for every entity to `delete`. So if you need to `delete` 10000 entities, then 10000 database round-trip will be performed which is **INSANELY** slow.
24
+
`SaveChanges`requires one database round-trip for every entity to `delete`. So if you need to `delete` 10000 entities, then 10000 database round-trips will be performed which is **INSANELY** slow.
25
25
26
-
`BulkDelete` in counterpart offer great customization and require the minimum database round-trip as possible.
26
+
`BulkDelete` in counterpart offers great customization and requires the minimum database round-trips as possible.
27
27
28
28
## Performance Comparisons
29
29
@@ -70,15 +70,15 @@ context.BulkDelete(customers, options => options.ColumnPrimaryKeyExpression = cu
70
70
{% endhighlight %}
71
71
72
72
### How can I include child entities (Entity Graph)?
73
-
You cannot. Due to the risk of mistake, we preferred our offering this options and make sure every entity you wish to `delete` is specified.
73
+
You cannot. Due to the risk of mistakes, we preferred not to offer this option and make sure every entity you wish to `delete` is specified.
74
74
75
75
### Why BulkDelete doesn't use the ChangeTracker?
76
-
To provide the best performance as possible!
76
+
To provide the best performance possible!
77
77
78
-
Since using the `ChangeTracker` can greatly reduce performance, we choose to let `BulkSaveChanges` method to handle scenario with `ChangeTracker` and `BulkDelete` scenario without it.
78
+
Since using the `ChangeTracker` can greatly reduce performance, we chose to let `BulkSaveChanges` method handle scenarios with `ChangeTracker` and `BulkDelete`, scenarios without it.
79
79
80
80
### Why BulkDelete is faster than BulkSaveChanges?
81
-
The major difference between both methods is `BulkSaveChanges`use the `ChangeTracker` but not the `BulkDelete` method.
81
+
The major difference between both methods is `BulkSaveChanges`uses the `ChangeTracker` but not the `BulkDelete` method.
82
82
83
83
By skipping the `ChangeTracker`, some methods like `DetectChanges` are no longer required which greatly helps to improve the performance.
`Inserting` thousand of entities for an initial load or a file importation is a typical scenario.
21
21
22
-
`SaveChanges`methods make quite impossible to handle this kind of situation directly from Entity Framework due to the number of database round-trips required.
22
+
`SaveChanges`method makes it quite impossible to handle this kind of situation directly from Entity Framework due to the number of database round-trips required.
23
23
24
-
`SaveChanges`require one database round-trip for every entity to `insert`. So if you need to `insert` 10000 entities, then 10000 database round-trip will be performed which is **INSANELY** slow.
24
+
`SaveChanges`requires one database round-trip for every entity to `insert`. So if you need to `insert` 10000 entities, then 10000 database round-trips will be performed which is **INSANELY** slow.
25
25
26
-
`BulkInsert` in counterpart require the minimum database round-trip as possible. By example under the hood for SQL Server, a simple`SqlBulkCopy` could be performed.
26
+
`BulkInsert` in counterpart requires the minimum database round-trips as possible. By example under the hood for SQL Server, a simple`SqlBulkCopy` could be performed.
Since using the `ChangeTracker` can greatly reduce performance, we choose to let `BulkSaveChanges` method to handle scenario with `ChangeTracker` and `BulkInsert`scenario without it.
81
+
Since using the `ChangeTracker` can greatly reduce performance, we chose to let `BulkSaveChanges` method handle the scenarios with `ChangeTracker` and `BulkInsert`the scenarios without it.
82
82
83
83
### Why BulkInsert is faster than BulkSaveChanges?
84
-
The major difference between both methods is `BulkSaveChanges`use the `ChangeTracker` but not the `BulkInsert` method.
84
+
The major difference between both methods is `BulkSaveChanges`uses the `ChangeTracker` but not the `BulkInsert` method.
85
85
86
86
By skipping the `ChangeTracker`, some methods like `Add`, `AddRange`, `DetectChanges` are no longer required which greatly helps to improve the performance.
Despite the `ChangeTracker` being outstanding to track what's modified, it lacks in term of scalability and flexibility.
23
23
24
-
`SaveChanges`require one database round-trip for every entity to `insert` or `update`. So if you need to `insert` or `update` 10000 entities, then 10000 database round-trip will be performed which is **INSANELY** slow.
24
+
`SaveChanges`requires one database round-trip for every entity to `insert` or `update`. So if you need to `insert` or `update` 10000 entities, then 10000 database round-trips will be performed which is **INSANELY** slow.
25
25
26
-
`BulkMerge` in counterpart offer great customization and require the minimum database round-trip as possible.
26
+
`BulkMerge` in counterpart offers great customization and requires the minimum database round-trips as possible.
Since using the `ChangeTracker` can greatly reduce performance, we choose to let `BulkSaveChanges` method to handle scenario with `ChangeTracker` and `BulkMerge` scenario without it.
111
+
Since using the `ChangeTracker` can greatly reduce performance, we chose to let `BulkSaveChanges` method handle scenarios with `ChangeTracker` and `BulkMerge`, scenarios without it.
Using the `ChangeTracker` to detect and persist change automatically is great! However, it leads very fast to some problem when multiples entities need to be saved.
35
+
Using the `ChangeTracker` to detect and persist changes automatically is great! However, it leads very fast to some problems when multiple entities need to be saved.
36
36
37
-
`SaveChanges` method makes a database round-trip for every change. So if you need to insert 10000 entities, then 10000 database round-trip will be performed which is INSANELY slow.
37
+
`SaveChanges` method makes a database round-trip for every change. So if you need to insert 10000 entities, then 10000 database round-trips will be performed which is INSANELY slow.
38
38
39
-
`BulkSaveChanges`work exactly like `SaveChanges` but reduce the number of database round-trips required to greatly helps to improve the performance.
39
+
`BulkSaveChanges`works exactly like `SaveChanges` but reduces the number of database round-trips required to greatly help improve the performance.
0 commit comments