Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RAM Usage #310

Closed
LindsayCole opened this issue Jun 7, 2016 · 14 comments
Closed

RAM Usage #310

LindsayCole opened this issue Jun 7, 2016 · 14 comments

Comments

@LindsayCole
Copy link

Plex Requests.Net Version:

1.7.5

Operating System:

Server 2012 R2

Not sure if this is normal or not, but after about 12 hours of use, PR is using 2.5GB of memory. My install had zero users at the time. And does not have a ton of requests pending.

Is this normal? Is there anyway I can designate it a certain amount of RAM? At one point, it was actually crashing Plex.

Thanks,

@tidusjar
Copy link
Member

tidusjar commented Jun 7, 2016

Set your log level to Warn, I have fixed this in the dev build. Release TBA

@LindsayCole
Copy link
Author

Thanks for the prompt response.

I changed to Warn, and I got this popup after submitting:

DataTables warning: table id=example - Ajax error. For more information about this error, please see http://datatables.net/tn/7

@tidusjar
Copy link
Member

tidusjar commented Jun 7, 2016

Really? :/ Can you send me your database please? plexrequests.sqlite to jamierees@outlook.com.

Thanks.

@LindsayCole
Copy link
Author

uhh, that file is 528MB.

I can provide remote access for you if you would like?

@LindsayCole
Copy link
Author

rpnet

@LindsayCole
Copy link
Author

528

@zenjabba
Copy link

zenjabba commented Jun 7, 2016

Wait till it grows to 1.5GB, and watch your system cry :)

@tidusjar
Copy link
Member

tidusjar commented Jun 7, 2016

It's the log files 😡

@zenjabba
Copy link

zenjabba commented Jun 7, 2016

tis all good. This program is making my life so much easier... Glad I can be here to help you make it better.

@LindsayCole
Copy link
Author

LindsayCole commented Jun 7, 2016

How would you like to proceed tidusjar?

That error doesn't seem to affect usability, and RAM usage is ~70MB since I made the change. So anything past this, is purely for helping this problem in the future ;)

@tidusjar
Copy link
Member

tidusjar commented Jun 7, 2016

Can I suggest to restore one of the backed up database files and just set the log level to error maybe?

On 7 Jun 2016, at 6:53 pm, LindsayCole notifications@github.com wrote:

How would you like to proceed tidusjar?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@LindsayCole
Copy link
Author

Those backs are from the previous version. How would that affect this
install?

On Tue, Jun 7, 2016 at 3:10 PM, Jamie notifications@github.com wrote:

Can I suggest to restore one of the backed up database files and just set
the log level to error maybe?

On 7 Jun 2016, at 6:53 pm, LindsayCole notifications@github.com
wrote:

How would you like to proceed tidusjar?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#310 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AOf2uJDSNmtKfjd9EB-dUs7nsaOtH8waks5qJbP_gaJpZM4Iv3ri
.

@tidusjar
Copy link
Member

tidusjar commented Jun 7, 2016

Should be fine, the databases usually stay mostly backwards compatible with the smaller increments.

On 7 Jun 2016, at 7:37 pm, LindsayCole notifications@github.com wrote:

Those backs are from the previous version. How would that affect this
install?

On Tue, Jun 7, 2016 at 3:10 PM, Jamie notifications@github.com wrote:

Can I suggest to restore one of the backed up database files and just set
the log level to error maybe?

On 7 Jun 2016, at 6:53 pm, LindsayCole notifications@github.com
wrote:

How would you like to proceed tidusjar?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#310 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AOf2uJDSNmtKfjd9EB-dUs7nsaOtH8waks5qJbP_gaJpZM4Iv3ri
.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@tidusjar
Copy link
Member

tidusjar commented Jun 8, 2016

I'm going to close this and use #313 as the master. I have already made lots of fixes in the dev build to resolve this issue (Including automatically setting the log level to Warn when you open the new version)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants