Skip to content

Is predition model thread safe? #421

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.

Sign up for GitHub

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

Jump to bottom
Closed
hanabi1224 opened this issue Jun 26, 2018 · 3 comments
Closed

Is predition model thread safe? #421

hanabi1224 opened this issue Jun 26, 2018 · 3 comments
Labels
API Issues pertaining the friendly API documentation Related to documentation of ML.NET question Further information is requested

Comments

@hanabi1224
Copy link

Should I use single instance or a pool of objects? Thanks in advance!
@GalOshri GalOshri added the question Further information is requested label Jun 27, 2018
@Ivanidzo4ka Ivanidzo4ka added API Issues pertaining the friendly API documentation Related to documentation of ML.NET labels Oct 18, 2018
@Ivanidzo4ka
Copy link
Contributor

DRI RESPONSE: Currently it's not thread safe.
@Zruty0 do we have any plans to make it thread safe? Do we have any examples in cookbook how to handle multi-threading?

@Zruty0
Copy link
Contributor

Zruty0 commented Oct 18, 2018 •
edited
Loading

We do not have any plans to make it thread-safe.
For multi-threading approaches, it's a somewhat complicated subject, so I didn't write docs on it. We probably should.

@CESARDELATORRE CESARDELATORRE mentioned this issue Nov 26, 2018
Closed
@CESARDELATORRE
Copy link
Contributor

Relating this issue with the one I'm explaining in detail:
#1718

So I'm closing this one.

@ghost ghost locked as resolved and limited conversation to collaborators Mar 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
API Issues pertaining the friendly API documentation Related to documentation of ML.NET question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@Ivanidzo4ka @CESARDELATORRE @GalOshri @hanabi1224 @Zruty0