Could be, but I don't think so in this particular case. The dataset is like
a few thousand rows and around 20 features.
2016-02-24 18:51 GMT+00:00 Sebastian Raschka :
> I am not using XGBoost and honestly don't much about the way its
> implemented. However, have you checked
I am not using XGBoost and honestly don't much about the way its implemented.
However, have you checked if memory swapping could be an issue if you are doing
multiprocessing? Maybe it's using so much RAM due to creating multiple copies
that it just feels like it stopped? Just a thought :P
> On
Hi Joel,
I ran lots of tests today and I realized that it is XGBRegressor (a wrapper
for XGboost) that is guilty. However, it doesn't always stop. It does only
some times. Any ideas why this might be happening?
2016-02-24 0:38 GMT+00:00 Joel Nothman :
> What estimator(s)
What estimator(s) are you searching over? How big is your data?
On 24 February 2016 at 06:15, Stylianos Kampakis <
stylianos.kampa...@gmail.com> wrote:
> Hi everyone,
>
> Sometimes, when I am using random search with n_jobs>1 the processing
> stops. I am on a Mac. I went through some discussions