-
Notifications
You must be signed in to change notification settings - Fork 538
Conversation
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
6 similar comments
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
Codecov Report
@@ Coverage Diff @@
## master #1405 +/- ##
==========================================
+ Coverage 85.13% 85.55% +0.42%
==========================================
Files 53 53
Lines 6928 6987 +59
==========================================
+ Hits 5898 5978 +80
+ Misses 1030 1009 -21
Continue to review full report at Codecov.
|
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
5 similar comments
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
Update testing.py Update testing.py Update testing.py Update testing.py Update testing.py Update testing.py Update testing.py Update testing.py Update testing.py Update testing.py Update testing.py Update testing.py Update testing.py Update testing.py Update testing.py Update attention_cell.py Update testing.py Update testing.py Update testing.py Update test_models_bert.py Update run_batch_squad.sh Update generate_commands.py Update run_batch_squad.sh Update run_batch_squad.sh Update run_batch_squad.sh Add region Update generate_commands.py Update run_squad.template Try to use clip 1.0 update Update README.md Update attention_cell.py Update benchmark_gluonnlp.py Update attention_cell.py Update testing.py Update run_squad.py Update attention_cell.py Update attention_cell.py Update attention_cell.py update Update attention_cell.py update Update numbers + log + weight update update Update testing.py
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
1 similar comment
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
scripts/question_answering/README.md
Outdated
### Run with AWS Batch | ||
We can quickly run the squad finetuning via the [AWS Batch support](../../tools/batch). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the batch support refactored so that it can be bootstrapped in any AWS account? including VPC setup, security group, etc?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if it doesn't work we should avoid advertising this as user facing feature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's for the purpose of running the experiments quickly if you have batch access. Otherwise, we will end up writing everything inside the batch folder.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's also ok to just keep the script somewhere local or in a gist.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've also considered this. The problem is that it will increase the communication time and it can add some values to the user if we will later have the cloudformation script.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if the feature doesn't work for a user as is, it will cause confusion and friction.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
keeping it as part of infra code is also ok.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May be let's still keep it in the batch folder.
#!/bin/bash | ||
|
||
set -ex | ||
|
||
LOG_PATH=$1 | ||
SAVE_DIR_NAME=${2:-squad_2.0} | ||
|
||
while read -r job_name job_id; do | ||
aws s3 sync s3://gluon-nlp-dev/batch/${job_id}/temp ${SAVE_DIR_NAME}/${job_name} | ||
done < ${LOG_PATH} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we should check in all the convenience scripts in the scripts folder, because this folder is user-facing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For me, I feel that it's fine to help reproduce the experiments for our own purpose. And also later add to the scheduled check.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be resolved now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
let's remove the non-user-facing scripts from the user facing scripts folder.
concerns addressed. great addition and a step closer to full prod support
The documentation website for preview: http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR1405/amp/index.html |
Description
Add AMP support + update benchmarking script.
Some issues:
Checklist
Essentials
cc @dmlc/gluon-nlp-team