TrueCloudLab/neoneo-go
7
0
Fork 2
Code Issues Pull requests Projects Releases Packages Wiki Activity

storage: don't use locks for memory batches

Browse source 
They're inherently single-threaded, so locking makes no sense for them.
This commit is contained in:
Roman Khimov 2021-08-11 18:53:18 +03:00
parent 0a2bbf3c04
commit 18682f2409
2 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
pkg/core/storage/memory_store.go
View file

@ -23,12 +23,12 @@ type MemoryBatch struct {
// Put implements the Batch interface. // Put implements the Batch interface.
func (b *MemoryBatch) Put(k, v []byte) { func (b *MemoryBatch) Put(k, v []byte) {
_ = b.MemoryStore.Put(k, v) b.MemoryStore.put(string(k), slice.Copy(v))
} }
// Delete implements Batch interface. // Delete implements Batch interface.
func (b *MemoryBatch) Delete(k []byte) { func (b *MemoryBatch) Delete(k []byte) {
_ = b.MemoryStore.Delete(k) b.MemoryStore.drop(string(k))
} }
// NewMemoryStore creates a new MemoryStore object. // NewMemoryStore creates a new MemoryStore object.

3
pkg/core/storage/store.go
View file

@ -52,7 +52,8 @@ type (
// Batch represents an abstraction on top of batch operations. // Batch represents an abstraction on top of batch operations.
// Each Store implementation is responsible of casting a Batch // Each Store implementation is responsible of casting a Batch
// to its appropriate type. // to its appropriate type. Batches can only be used in a single
// thread.
Batch interface { Batch interface {
Delete(k []byte) Delete(k []byte)
Put(k, v []byte) Put(k, v []byte)