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

Can you use Graphene without a corefencer? #53

Open
clement1234567891011 opened this issue May 18, 2022 · 4 comments
Open

Can you use Graphene without a corefencer? #53

clement1234567891011 opened this issue May 18, 2022 · 4 comments

Comments

@clement1234567891011
Copy link

Hi,
I keep getting java.lang.OutOfMemoryError: Java heap space even after using -Xmx4G just when initialising Graphene(). I don't intend to use co-referencing. Is there a way to speed up initialisation (and get around the heap space error) but just not initialising the coreferencer? I've tried with Graphene(null) but noticed that it doesn't work at all.

Many thanks for any tips!
Clement

@Aatlantise
Copy link

Aatlantise commented May 25, 2022

I believe you can--

On Graphene-server with the following setting:
"doCoreference": "false"

And on Graphene-CLI with the following flag:
--doCoreference false

Let me know if that works.
Junghyun

@clement1234567891011
Copy link
Author

Sorry, I was looking for the option when calling the API from Java. Any options there too?
Many thanks!

@bermeitinger-b
Copy link
Member

Graphene-Core currently doesn't have this possibility to not instantiate it without a coreference resolver.

However, you could set the config to load pycobalt and set it to an unrouted address (0.0.0.0). If you then always call the API without using coreference solution (doCoreference=false as parameter) there shouldn't be a problem.

@clement1234567891011
Copy link
Author

Great, yes, this worked like a charm! Many thanks!

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

3 participants