Introduce queue for prepared objects #128

New issue

Open

opened 2023-07-25 10:35:41 +00:00 by fyrchik · 2 comments

fyrchik commented

2023-07-25 10:35:41 +00:00

Owner

REP4, 1G object, dev-env

Here is an old trace -- 74 sec (master):

Here is a trace after basic parallelization -- 48 sec (send-and-forget at most 3 parts in parallel, collect errors later):

There is a tradeoff between parallelization and memory consumption on the client: I suggest to introduce a parameter for SDK here (default=1).

Can serve as a basis for a later geo-aware placement.

REP4, 1G object, dev-env Here is an old trace -- 74 sec (master): ![image](/attachments/a6efcffa-4636-41bd-876e-c1abffcc527e) Here is a trace after basic parallelization -- 48 sec (send-and-forget at most 3 parts in parallel, collect errors later): ![image](/attachments/75547815-e1cc-47d4-bb39-a963cc8130a1) There is a tradeoff between parallelization and memory consumption on the client: I suggest to introduce a parameter for SDK here (default=1). Can serve as a basis for a later geo-aware placement.

image.png

157 KiB

image.png

158 KiB

fyrchik commented

2023-07-25 10:38:16 +00:00

Author

Owner

Oh, it seems I have homomorphic hashing enabled -- it explains some gaps on pictures.