Performance issues in your project (by P3) #2
Comments
|
Hello, I'm looking forward to your reply~ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
{{ message }}
Hello! I've found a performance issue in your project:
batch()should be called beforemap(), which could make your program more efficient. Here is the tensorflow document to support it.Detailed description is listed below:
.batch(128)(here) should be called before.map(preprocess)(here)..batch(64)(here) should be called before.map(preprocess)(here)..batch(512)(here) should be called before.map(preprocess)(here)..batch(512)(here) should be called before.map(preprocess)(here)..batch(batchsz)(here) should be called before.map(preprocess)(here)..batch(batchsz)(here) should be called before.map(preprocess)(here)..batch(batchsz)(here) should be called before.map(preprocess)(here)..batch(32)(here) should be called before.map(preprocess)(here)..batch(batchsz)(here) should be called before.map(preprocess)(here)..batch(batchsz)(here) should be called before.map(preprocess)(here)..batch(batchsz)(here) should be called before.map(preprocess)(here)..batch(128)(here) should be called before.map(proprocess)(here)..batch(128)(here) should be called before.map(proprocess)(here).Besides, you need to check the function called in
map()(e.g.,proprocesscalled in.map(proprocess)) whether to be affected or not to make the changed code work properly. For example, ifproprocessneeds data with shape (x, y, z) as its input before fix, it would require data with shape (batch_size, x, y, z).Looking forward to your reply. Btw, I am very glad to create a PR to fix it if you are too busy.
The text was updated successfully, but these errors were encountered: