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

Back-end performance degradation when importing CSV files with 100+ transactions #1543

Open
yiliev0 opened this issue Feb 12, 2025 · 0 comments
Open

Back-end performance degradation when importing CSV files with 100+ transactions #1543

yiliev0 opened this issue Feb 12, 2025 · 0 comments
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs

Comments

@yiliev0
Copy link
Contributor

yiliev0 commented Feb 12, 2025 •
edited
Loading

Description

When importing CSV files containing more than 100 transactions, the backend initiates a large number of operations simultaneously, which leads to performance degradation. This congestion may result in system unresponsiveness.
groupTransactions.csv

Steps to reproduce

  1. Prepare a CSV file with 100+ transaction records.
  2. Upload a csv in transaction group
  3. Monitor the backend activity

Additional context

No response

Hedera network

No response

Version

0.9.0

Operating system

None
@yiliev0 yiliev0 added the Bug A error that causes the feature to behave differently than what was expected based on design docs label Feb 12, 2025
@yiliev0 yiliev0 changed the title Backend Performance Degradation When Importing CSV Files with 100+ Transactions Back-end performance degradation when importing CSV files with 100+ transactions Feb 12, 2025
@jbair06 jbair06 mentioned this issue Feb 12, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug A error that causes the feature to behave differently than what was expected based on design docs
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yiliev0