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.

Sign up for GitHub

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

Jump to bottom

Optimizing String representation for STEP #71

Open
dpasukhi opened this issue Sep 20, 2024 · 0 comments
Open

Optimizing String representation for STEP #71

dpasukhi opened this issue Sep 20, 2024 · 0 comments
Assignees
@dpasukhi
Labels
1. Data Exchange Import/Export or iterating of the CAD data 2. Enhancement New feature or request

Comments

@dpasukhi
Copy link
Member

For now Handle(NCollection_HAsciiString) takes at least 32b per object on dynamic memory.
Needs to find a way to improve and use at least 18b per object. And cache the empty strings.
One of the idea - avoid Standard_Transient and any virtual functionality.
Smart pointer needs to be as a internal object. The sample TopoDS_Shape.
@dpasukhi dpasukhi added 2. Enhancement New feature or request 1. Data Exchange Import/Export or iterating of the CAD data labels Sep 20, 2024
@dpasukhi dpasukhi self-assigned this Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dpasukhi dpasukhi

Labels
1. Data Exchange Import/Export or iterating of the CAD data 2. Enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dpasukhi