Skip to content
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

add vectorization options as a goal target #2483

Merged
merged 4 commits into from
Jun 28, 2023

Conversation

mikebrow
Copy link
Contributor

Consider closing #810 in concert with fix #2419

The original issue mentioned a performance problem and a suggestion for going beyond the simple test loop to vectorizing the processing in some form, batch / parallel etc.

However, fix 2419 linked above, addressed the performance problem by switching from always cpu to device and by correcting other inconsistencies. Thanks!

Further, this is targeted as a beginner example, and with the above corrections I believe this example now stands on it's own as is.

Description

This change merely proposes to the reader, in the where to go section, that:

# A further direction to go, depending on available resources, is to modify
# the code to support processing work in batch, in parallel, and or distributed
# vs. working on one attack at a time in the above for each epsilon test() loop.

Checklist

  • The issue that is being fixed is referred in the description (see above "Fixes #ISSUE_NUMBER")
  • Only one issue is addressed in this pull request
  • Labels from the issue that this PR is fixing are added to this pull request
  • No unnecessary issues are included into this pull request.

Signed-off-by: Mike Brown <brownwm@us.ibm.com>
@pytorch-bot
Copy link

pytorch-bot bot commented Jun 23, 2023

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/tutorials/2483

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit f223648:
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@netlify
Copy link

netlify bot commented Jun 23, 2023

Deploy Preview for pytorch-tutorials-preview ready!

Name Link
🔨 Latest commit f223648
🔍 Latest deploy log https://app.netlify.com/sites/pytorch-tutorials-preview/deploys/649c561092b07e0008286cd3
😎 Deploy Preview https://deploy-preview-2483--pytorch-tutorials-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

#
# A further direction to go, depending on available resources, is to modify
# the code to support processing work in batch, in parallel, and or distributed
# vs. working on one attack at a time in the above for each epsilon test() loop.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you want to add examples of those?

Copy link
Contributor Author

@mikebrow mikebrow Jun 23, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thought about it and was thinking this example is more a beginner example and is currently the appropriate size for this section.. Perhaps a second example addressing one or more of the above concerns is warranted and we could link from here?

@svekars svekars merged commit dee4797 into pytorch:main Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants