summaryrefslogtreecommitdiffstats
path: root/include/framework/structure/MutableBuffer.h
Commit message (Collapse)AuthorAgeFilesLines
* Updates/progress towards succinct trie supportDouglas Rumbaugh2024-03-201-2/+3
|
* MutableBuffer: Allow hwm to equal lwmDouglas Rumbaugh2024-02-121-1/+1
| | | | | The high watermark and low watermark can now be equal, to allow for blocking reconstruction without requiring odd buffer sizes.
* BufferView: Adjusted BV to avoid repeated modulus operationsDouglas Rumbaugh2024-02-051-5/+8
|
* Insert throughput benchmarkDouglas Rumbaugh2024-01-311-1/+1
|
* Multiple concurrency bug fixesDouglas Rumbaugh2024-01-171-21/+37
| | | | | | | | A poorly organized commit with fixes for a variety of bugs that were causing missing records. The core problems all appear to be fixed, though there is an outstanding problem with tombstones not being completely canceled. A very small number are appearing in the wrong order during the static structure test.
* Use 16-byte CAS to control buffer headDouglas B. Rumbaugh2024-01-151-61/+59
|
* Various single-threaded bug fixesDouglas B. Rumbaugh2024-01-151-4/+22
|
* Fixed some potential buffer-related concurrency bugsDouglas Rumbaugh2024-01-111-43/+63
|
* MutableBuffer: multithreaded insert test + bugfixesDouglas Rumbaugh2024-01-101-4/+9
|
* MutableBuffer+View: Implementation with unit testsDouglas Rumbaugh2024-01-101-35/+98
|
* Initial update of buffer to new specificationsDouglas B. Rumbaugh2024-01-091-79/+37
| | | | | | | | | | | | | | | | | | | There are a few minor issues that this introduces, however. Global tracking of a lot of secondary information, such as weights for WIRS/WSS, or the exact number of tombstones will need to be approached differently than they have been historically with this new approach. I've also removed most of the tombstone capacity related code. We had decided not to bother enforcing this at the buffer level anyway, and it would greatly increase the complexity of the problem of predicting when the next compaction will be. On the whole this new approach seems like it'll simplify a lot. This commit actually removes significantly more code than it adds. One minor issue: the currently implementation will have problems in the circular array indexes once more than 2^64 records have been inserted. This doesn't seem like a realistic problem at the moment.
* Refactoring: corrected a number of names and added more commentsDouglas Rumbaugh2023-12-131-6/+12
|
* Tombstone Compaction: re-enabled tombstone compactionDouglas Rumbaugh2023-11-131-1/+1
| | | | | | | Currently, proactive buffer tombstone compaction is disabled by forcing the buffer tombstone capacity to match its record capacity. It isn't clear how to best handle proactive buffer compactions in an environment where new buffers are spawned anyway.
* Comment and License updatesDouglas Rumbaugh2023-11-071-1/+1
|
* MutableBuffer: added explicit tail variableDouglas Rumbaugh2023-11-061-5/+12
| | | | | | | Use an explicit m_tail variable for insertion, rather than using m_reccnt. This ensures that the record count doesn't increase despite new records being inserted, and allows for the m_tail variable to be decremented on failure without causing the record count to momentarily change.
* MutableBuffer: removed most concurrency control stuffDouglas B. Rumbaugh2023-10-311-49/+10
| | | | | | The buffer isn't responsible for a lot of CC anymore (just the append operation), so this code was no longer necessary. Also removed the only calls to some of these CC operations within the rest of the framework.
* General Comment + Consistency updatesDouglas Rumbaugh2023-10-301-2/+2
|
* Began moving to an explicit epoch-based systemDouglas Rumbaugh2023-10-231-0/+4
| | | | | | | I started moving over to an explicit Epoch based system, which has necessitated a ton of changes throughout the code base. This will ultimately allow for a much cleaner set of abstractions for managing concurrency.
* BugfixesDouglas Rumbaugh2023-10-231-0/+1
|
* Initial pass w/ new scheduler setupDouglas Rumbaugh2023-10-201-0/+11
| | | | currently there's a race condition of some type to sort out.
* Re-structuring Project + scheduling updatesDouglas Rumbaugh2023-09-251-0/+242
This is a big one--probably should have split it apart, but I'm feeling lazy this morning. * Organized the mess of header files in include/framework by splitting them out into their own subdirectories, and renaming a few files to remove redundancies introduced by the directory structure. * Introduced a new framework/ShardRequirements.h header file for simpler shard development. This header simply contains the necessary includes from framework/* for creating shard files. This should help to remove structural dependencies from the framework file structure and shards, as well as centralizing the necessary framework files to make shard development easier. * Created a (currently dummy) SchedulerInterface, and make the scheduler implementation a template parameter of the dynamic extension for easier testing of various scheduling policies. There's still more work to be done to fully integrate the scheduler (queries, multiple buffers), but some more of the necessary framework code for this has been added as well. * Adjusted the Task interface setup for the scheduler. The task structures have been removed from ExtensionStructure and placed in their own header file. Additionally, I started experimenting with using std::variant, as opposed to inheritence, to implement subtype polymorphism on the Merge and Query tasks. The scheduler now has a general task queue that contains both, and std::variant, std::visit, and std::get are used to manipulate them without virtual functions. * Removed Alex.h, as it can't build anyway. There's a branch out there containing the Alex implementation stripped of the C++20 stuff. So there's no need to keep it here.