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

how can i solve the problem of save Json file(river strategy cannot work)) #169

Open
l13985129543 opened this issue Jun 6, 2023 · 5 comments

Comments

@l13985129543
Copy link

appreciate for your project!but how can i save the Json file for the river actions?(range2 works,but range3 will out of memory,my coding env is Windows+qt5.15) please help!

@bupticybee
Copy link
Owner

set "dump_round" to 3 will solve the proble, if you are using gui, tune it in setting.

If you are encountering OOM when dumping the strategy file, it's a bug. Sorry but there is nothing can be done at this point of time.

@nguyenviettuan96
Copy link

hi bupticybee is that ok to save json 3 rounds for short deck

@bupticybee
Copy link
Owner

hi bupticybee is that ok to save json 3 rounds for short deck

Yeah that's okay for sure, but it would become very slow.

@nguyenviettuan96
Copy link

hi bupticybee is that ok to save json 3 rounds for short deck

Yeah that's okay for sure, but it would become very slow.

I look your code at retConvertJson func, which is recursion. That is a reason for slowing. So what I can do to reduce time is that changing json to dictionary( map in c++). What do u think a bout that

@AlexBuathier
Copy link

AlexBuathier commented Apr 24, 2024

set "dump_round" to 3 will solve the proble, if you are using gui, tune it in setting.

If you are encountering OOM when dumping the strategy file, it's a bug. Sorry but there is nothing can be done at this point of time.

when we try to record with the river the RAM fills indefinitely until reaching OOM.
I solve a hand that requires 15GB of RAM and when the dump starts, the RAM fills up indefinitely until it reaches my 96GB

Is there a way to get around this memory leak? (I use only console version)

image

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

No branches or pull requests

4 participants