-
Notifications
You must be signed in to change notification settings - Fork 99
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
Append creates very slow node to read #2093
Comments
hi @giuse88, It does seems slower than expected though, so I will investigate further. |
This is a bit weird I thought the data scruture would be the same between a write and append. ! Apart from what you suggested, isn’t there a possibility to turn off this behaviour? The other things I've noticed is that I am creating a version for each append. Is it possible to turn it off? |
Does artic db support write with an index? |
It is not possible to turn off the behavior for append, it is intentional that every new 'write' operation creates a new version (e.g. write, append, update.
I am not sure what you mean by this, we support writing data frames to symbols.
|
Hi @G-D-Petrov , thank you for your help. I started to use lmdb as backend to improve the performance, and the difference is speed is much better and I will also do what you suggested. However I've noticed another diffrence between append and write. Append seems to create massive file. I've a a library which is ~2M of data but arctic is using 166M to save it! If I copy this library into a new one with a single write the size is less than 1M. Is this expected behaviour? |
Just for reference, versions & snapshots are off. No extra data is created |
Describe the bug
Hi,
I noticed that when I append a dataframe to a node, the read of that node becomes very very slow. To clarify the problem, this is the code which reproduce the problem:
output:
You can see that reading the data from the appended node takes 47s.
The library is exactly the same, the problem is the append function.
Expected Results
The read takes the same amount of time.
OS, Python Version and ArcticDB Version
Python: 3.11.11 (main, Dec 4 2024, 08:55:08) [GCC 13.2.0]
OS: Linux-6.8.0-1018-aws-x86_64-with-glibc2.39
ArcticDB: 5.1.2
Backend storage used
AWS S3
Additional Context
None
The text was updated successfully, but these errors were encountered: