mirror of
https://github.com/quasar/Quasar.git
synced 2026-04-26 07:45:57 +03:00
[PR #263] [CLOSED] BufferManager implementation #1064
Labels
No labels
bug
bug
cant-reproduce
discussion
duplicate
easy
enhancement
help wanted
improvement
invalid
need more info
pull-request
question
wont-add
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Quasar#1064
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/quasar/Quasar/pull/263
Author: @yankejustin
Created: 6/5/2015
Status: ❌ Closed
Base:
master← Head:NewBuff📝 Commits (1)
e8fcc23Implemented a BufferManager📊 Changes
4 files changed (+15 additions, -6 deletions)
View changed files
📝
Server/Core/Client.cs(+6 -4)📝
Server/Core/Helper/FileSplit.cs(+1 -1)📝
Server/Core/Server.cs(+7 -1)📝
Server/Server.csproj(+1 -0)📄 Description
Changes
1. Implemented a BufferManager object to handle client's buffers.Effects
- Use of a BufferManager class on the server to handle clients' buffers will greatly improve performance and memory resourcefulness. When a client is being disconnected or disposed of, we can return the allocated buffer back to the BufferManager so that it can be re-used. The concept behind this is that, instead of throwing away these expensive buffers, just keep them for other clients that can use them in the future.Note on memory usage:
While high memory usage is likely (though less-likely), the Garbage Collector will run its course if we must have some more memory. The memory we really need to worry about will now be managed better by using this object to mess with the buffers. :)
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.