-
Notifications
You must be signed in to change notification settings - Fork 24
tutorial(server): Add tutorial on server configurations #2859
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
base: main
Are you sure you want to change the base?
Conversation
|
Some tests with 'continue-on-error: true' have failed:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2859 +/- ##
=======================================
Coverage 84.43% 84.43%
=======================================
Files 92 92
Lines 10922 10922
=======================================
Hits 9222 9222
Misses 1700 1700 |
| ---------------------------------- | ||
|
|
||
| The default and most efficient way to use PyDPF-Core is with an :class:`InProcessServer <ansys.dpf.core.server_types.InProcessServer>`. | ||
| This configuration runs the DPF server directly within your Python process, eliminating data |
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.
We should maybe comment that a negative side of InProcess is that for it to properly work with all DPF plugins, a prerequisite is that all the runtime dependencies need to be compatible with the runtime dependencies with all Python dependencies. If there is any Python dependency with symbols collision with any DPF plugin, this plugin will not be loaded, thus loosing the capabilities added with this plugin. This limitation is not found in gRPC, where process isolation ensures dependency isolation
|
|
||
| Starting with Ansys 2026 R1 (DPF 2026.1.0) and PyDPF-Core 0.15.0, DPF Server gRPC | ||
| connections default to using authenticated mTLS (mutual TLS) transport for enhanced security. | ||
| This change also applies to service packs for Ansys 2025 R2 SP03, 2025 R1 SP04, and 2024 R2 SP05. |
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.
| This change also applies to service packs for Ansys 2025 R2 SP03, 2025 R1 SP04, and 2024 R2 SP05. | |
| This change also applies to service packs for Ansys 2025 R2 SP03 and SP04, 2025 R1 SP04, and 2024 R2 SP05. |
| requiring maximum performance and minimal memory overhead (default since Ansys 2023 R1) | ||
|
|
||
| - Use :class:`GrpcServer <ansys.dpf.core.server_types.GrpcServer>` when you need distributed | ||
| computation, remote access, or when running DPF on a different machine (available since Ansys 2022 R2) |
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.
| computation, remote access, or when running DPF on a different machine (available since Ansys 2022 R2) | |
| computation, remote access, symbols isolation, or when running DPF on a different machine (available since Ansys 2022 R2) |
|
@PProfizi Thanks for this, I've added a couple of comments |
No description provided.