-
Notifications
You must be signed in to change notification settings - Fork 96
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
Memory Issue #10
Comments
@MatteoTomassetti This is an out of memory issue |
I changed the code to do iterative training with a generator. It now runs
nicely on my laptop without needing to limit the amount of data!
You might still need to limit the batch size to fit your specific memory
availability.
…On Feb 28, 2017 1:53 AM, "Parth Mehta" ***@***.***> wrote:
This is an out of memory issue
I believe reducing the batch size to 25-50 should solve it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#10 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA9lwTvjoq-ooLNhyzh1QRNh1XAuhqiCks5rg2HrgaJpZM4MHfwQ>
.
|
thanks @parth126 and @MajorTal! I was wondering, based on your experience, what's the average running time I should expect for one epoch to train the entire |
I just moved to the news.2013.en.shuffled (much larger) - I'll update the code to reflect that. |
@MatteoTomassetti @MajorTal I was running this exact code with the default news.2013.en.shuffled dataset (changed almost nothing except to update Keras API calling to newer version and adapt the code to be python 3 compatible). After almost 2 days of training (on reasonable speed, was using Azure with K80) the accuracy is stuck at about 47-48%. I also noticed that while it had been able to fix many spelling mistakes, it always repeat the last character or just add trailing periods to the prediction and therefore marked as wrong. Do you have any idea what could be happening? I have been looking around and could not find good answer. |
If I recall correctly, the trailing periods are how I used to signal the
end of the sequence and they should be stripped off.
Also - I don't remember if the hyperparameters are optimized in any way in
the latest code. I changed the data significantly so that I can open source
the code from the version we used internally.
Thanks,
Tal Weiss
+31-6-1165-8778
Skype: major.tal
https://twitter.com/majortal
…On Thu, Nov 16, 2017 at 4:20 PM, FMFluke ***@***.***> wrote:
@MatteoTomassetti <https://github.com/matteotomassetti> @MajorTal
<https://github.com/majortal> I was running this exact code with the
default news.2013.en.shuffled dataset (changed almost nothing except to
update Keras API calling to newer version and adapt the code to be python 3
compatible). After almost 2 days of training (on reasonable speed, was
using Azure with K80) the accuracy is stuck at about 47-48%. I also noticed
that while it had been able to fix many spelling mistakes, it always repeat
the last character or just add trailing periods to the prediction and
therefore marked as wrong. Do you have any idea what could be happening? I
have been looking around and could not find good answer.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA9lwXa8tiAXnktUMMzpOe21hYhFTsAQks5s3FK4gaJpZM4MHfwQ>
.
|
Ok, but then how did you make the model know to exclude those periods when calculating the accuracy? How exactly did you strip them off? |
Hi,
Thank you for sharing your code publicly, but I'm having some memory issues when running it on AWS.
I'm spinning a g2.2xlarge instance on AWS and try to run your code for only the first 1000 lines of
news.2011.en.shuffled
.Have you ever got an error message like this one (see below)? And if so, is there a way to change the parameters to avoid or maybe should I select another type of AWS instance?
Just for completeness these are the parameters I was trying to test
And this is the error that I'm getting
The text was updated successfully, but these errors were encountered: