Revise for better performance. #34
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
#18 is linked to this PR, as if it fixes the issue. But if I understand correctly, the issue is not fixed, right? |
Ah, I thought I had fixed that but now I did for real. |
* Eliminates contracts in favor of inline checks. * Specializes multiple-value code to improve single-value performance (see racket/racket#4942). * Use simpler non-recursive growth computation (taken from Rust's Vector implementation). * Avoid duplicate work in core operations. * Add #:capacity arguments. * Use unsafe operations. * Use `vector-extend` from racket/racket#4943.
|
Performance compared to mut-treelist before: After: |
|
This is ready to merge, right? |
|
From my perspective yes although I was hoping for a review from @rmculpepper |
rmculpepper
requested changes
Mar 10, 2024
There was a problem hiding this comment.
Gvectors were previously unsynchronized and so not thread-safe. The introduction of unsafe operations makes them potentially memory-unsafe, and we need to make sure gvector operations, even used concurrently, are still memory-safe.
The gv-ensure-space! pattern helps: it means that writes to the vector have enough space, whether or not that vector is actually installed as the gvector's vec field at the end of the operation (eg, because of two racing add operations). I'm worried about the write to n afterwards; in a race, it might point past the end of vec.
I've pointed out a problem in gvector-ref if there is a concurrent call that shrinks the gvector. It also occurs if n is greater than the length of the vector. Other read operations (iteration, for example) might have similar problems, but I haven't checked them all.
If unsafe operations are used, we need to figure out and document invariants and patterns of field updates that actually preserve memory-safety.
| (define v (ensure-free-space-vec! (gvector-vec gv) (gvector-n gv) needed-free-space)) | ||
| (when v (set-gvector-vec! gv v))) | ||
|
|
||
| (define-syntax-rule (gv-ensure-space! gv n v needed-free-space) |
There was a problem hiding this comment.
I think a syntax like (define/ensure-space! (n v) gv needed-free-space) would better signal what this macro is doing.
| (unless (exact-nonnegative-integer? index) | ||
| (raise-type-error 'gvector-ref "exact nonnegative integer" index)) | ||
| (if (< index (gvector-n gv)) | ||
| (vector-ref (gvector-vec gv) index) | ||
| (unsafe-vector*-ref (gvector-vec gv) index) |
There was a problem hiding this comment.
I think this is unsafe if a concurrent call to remove shrinks the vector. That is, if (gvector-n gv) in the previous line is fetched before the call to remove and (gvector-vec gv) is fetched afterwards, the n might be stale and the vector can be too short.
| (cond [(eq? default none) | ||
| (check-index 'gvector-ref gv index #f)] | ||
| [(procedure? default) (default)] | ||
| [else default]))) | ||
|
|
||
| ;; gvector-set! with index = |gv| is interpreted as gvector-add! | ||
| (define (gvector-set! gv index item) | ||
| (check-gvector 'gvector-set gv) |
There was a problem hiding this comment.
should be 'gvector-set!
| (gvector-add! gv item) | ||
| (vector-set! (gvector-vec gv) index item)))) | ||
| (if (unsafe-fx= index n) | ||
| (unsafe-gvector-add! gv item) |
There was a problem hiding this comment.
I don't see why unsafe-gvector-add!'s precondition (not a chaperone) is satisfied here.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
single-value performance (see Optimizations and benchmarks for gvectors racket#4942).
(taken from Rust's Vector implementation).
vector-extendfrom Addvector-extend. racket#4943.