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

Performance impact of dynamic type mapping #26

Open
galarlo opened this issue Oct 25, 2021 · 0 comments
Open

Performance impact of dynamic type mapping #26

galarlo opened this issue Oct 25, 2021 · 0 comments

Comments

@galarlo
Copy link

galarlo commented Oct 25, 2021

I've glanced at the code of this library, and seen that it uses reflection to find the objects' fields.

Suppose I would implement a bulk inserter that's hardcoded for a specific type. What would be the performance difference relative to Dapper.Bulk? (An order of magnitude approximation would help too)

The relevant object has about 30 fields.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@galarlo