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.
Longtail_StorageAPI.OpenAppend
added toLongtail_StorageAPI
to open files without truncating existing dataLongtail_CreateConcurrentChunkWriteAPI
changed to takesource_version_index
andversion_diff
Longtail_ConcurrentChunkWriteAPI
refactored to use asset index and open/close files instead of keeping all open during entire lifetimeLongtail_ConcurrentChunkWriteAPI.CreateDir
now takes asset index instead of version local pathLongtail_ConcurrentChunkWriteAPI.Open
now takes asset index instead of version local path and droppingchunk_write_count
parameterLongtail_ConcurrentChunkWriteAPI.Write
now takes asset index instead of version local path and droppingchunk_write_count
parameterLongtail_SetMonitor
callback functions refactored to accomodate changes inLongtail_ConcurrentChunkWriteAPI
Longtail_GetRWLockSize
Longtail_CreateRWLock
Longtail_DeleteRWLock
Longtail_LockRWLockRead
Longtail_LockRWLockWrite
Longtail_UnlockRWLockRead
Longtail_UnlockRWLockWrite
Longtail_ChangeVersion2
execution causing Out Of Disk space errors.The changes also improves performance for more common cases with smaller archive sizes (60 Gb raw data/many files) but causes a small regression compared to 0.4.1 for archives with many very large files. It is still performing much more reasonable than 0.4.0 for these cases.