Commit 4d4e748
committed
Reset the peak memory usage for each job in BackgroundQueuePerformAction
This is specifically implemented in the controller instead of the
BackgroundQueueHandler, since the controller only has a single purpose:
Executing multiple different and a-priori unknown jobs. Measuring the peak
memory usage of the entire request is not useful there.
For other, user-facing, controllers the peak memory usage of an entire request
is more meaningful, since they also perform other tasks besides executing
background jobs. Thus we do not perform the reset in a generic location.1 parent 0024fb2 commit 4d4e748
1 file changed
Lines changed: 7 additions & 0 deletions
Lines changed: 7 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
29 | 29 | | |
30 | 30 | | |
31 | 31 | | |
| 32 | + | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
| 36 | + | |
| 37 | + | |
| 38 | + | |
32 | 39 | | |
33 | 40 | | |
34 | 41 | | |
| |||
0 commit comments