# Updates on Test Data

**URL:** <https://forum.storj.io/t/updates-on-test-data/26034>\
**Category:** Announcements\
**Created:** [April 30, 2024, 3:36pm UTC](https://forum.storj.io/t/updates-on-test-data/26034 "2024-04-30T15:36:45Z")\
**Posts on this page:** 20\
**Page:** 24

<div class="post-metadata">

**Author:** ![flwstern](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/flwstern/32/7821_2.png) [@flwstern](https://forum.storj.io/u/flwstern)\
**Post date:** [May 31, 2024, 11:20pm UTC](https://forum.storj.io/t/updates-on-test-data/26034/539 "2024-05-31T23:20:54Z")

</div>

how long is this test running approx?

---

<div class="post-metadata">

**Author:** ![Mitsos](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mitsos/32/1125_2.png) [@Mitsos](https://forum.storj.io/u/Mitsos)\
**Post date:** [May 31, 2024, 11:25pm UTC](https://forum.storj.io/t/updates-on-test-data/26034/540 "2024-05-31T23:25:09Z")

</div>

I bet next week we’ll be testing AMD vs Intel performance.

---

<div class="post-metadata">

**Author:** ![pangolin](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/pangolin/32/15685_2.png) [@pangolin](https://forum.storj.io/u/pangolin)\
**Post date:** [May 31, 2024, 11:45pm UTC](https://forum.storj.io/t/updates-on-test-data/26034/541 "2024-05-31T23:45:40Z")

</div>

I guess many problems (high ram usage, crashes) could be avoided by just setting storage2.max-concurrent-requests to a reasonable value.

---

<div class="post-metadata">

**Author:** ![Knowledge](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/knowledge/32/10681_2.png) [@Knowledge](https://forum.storj.io/u/Knowledge)\
**Post date:** [June 1, 2024, 12:13am UTC](https://forum.storj.io/t/updates-on-test-data/26034/542 "2024-06-01T00:13:44Z")

</div>

Littleskunk may be able to answer that, but when some of these customers sign on, the current conditions “may” be the new normal. If your nodes are restarting/crashing or the traffic load is too much for your current configuration you may want to work on addressing it now while these tests are ongoing.

---

<div class="post-metadata">

**Author:** ![littleskunk](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/littleskunk/32/63_2.png) [@littleskunk](https://forum.storj.io/u/littleskunk)\
**Post date:** [June 1, 2024, 12:14am UTC](https://forum.storj.io/t/updates-on-test-data/26034/543 "2024-06-01T00:14:54Z")

</div>

> [@Andrew](#):
>
> It would be good to know when the developers plan to finally finish these tests.

There are only 2 reasons to stop the test.

1. No deals are getting signed.
2. Deals are getting signed and the test traffic gets replaced with real traffic.

---

<div class="post-metadata">

**Author:** ![zip](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/zip/32/7813_2.png) [@zip](https://forum.storj.io/u/zip)\
**Post date:** [June 1, 2024, 12:54am UTC](https://forum.storj.io/t/updates-on-test-data/26034/544 "2024-06-01T00:54:31Z")

</div>

> [@Knowledge](#):
>
> If your nodes are restarting/crashing or the traffic load is too much for your current configuration you may want to work on addressing it now while these tests are ongoing.

Exactly.  
I’m grateful for these tests as this is a great opportunity to realise what works, what doesn’t and to fine tune the setup.  
I just wish the days would be 48 hours long 😐.  
And I also like to molest the ISP 🙂.

---

<div class="post-metadata">

**Author:** ![Andrew](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/andrew/32/1139_2.png) [@Andrew](https://forum.storj.io/u/Andrew)\
**Post date:** [June 1, 2024, 12:58am UTC](https://forum.storj.io/t/updates-on-test-data/26034/545 "2024-06-01T00:58:01Z")

</div>

> [@littleskunk](#):
>
> There are only 2 reasons to stop the test.
> 
> 1. No deals are getting signed.
> 2. Deals are getting signed and the test traffic gets replaced with real traffic.

Are you trying to say that this is the new normal? We have had enough bugs in the last few months that still haven’t been properly fixed and still cause a lot of problems, and now this?

---

<div class="post-metadata">

**Author:** ![Roxor](https://storj.bcdn.literatehosting.com/letter_avatar/roxor/32/6_22734026db12803ebb3e059622ac3534.png) [@Roxor](https://forum.storj.io/u/Roxor)\
**Post date:** [June 1, 2024, 1:05am UTC](https://forum.storj.io/t/updates-on-test-data/26034/546 "2024-06-01T01:05:59Z")

</div>

> [@Andrew](#):
>
> Are you trying to say that this is the new normal? We have had enough bugs in the last few months that still haven’t been properly fixed and still cause a lot of problems, and now this?

Doesn’t the very first post in this thread, from a month ago, say “_We don’t expect that this load is temporary, and may in fact be the new normal. Please take steps to correct issues your nodes may have keeping up with this load…_”?

So, plenty of warning and no surprises?

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [June 1, 2024, 5:56am UTC](https://forum.storj.io/t/updates-on-test-data/26034/547 "2024-06-01T05:56:15Z")

</div>

> [@Ruskiem](#):
>
> we had some cases of memory leak back in the days 2021 or so, but the problem was solved.

I do not remember it… Could you please find an info?  
Usually the high RAM usage is related to a slow disks. My docker for Windows nodes uses about 1-2GB (because disks are network connected, even if that is locally), the Windows service only 300MB.

---

<div class="post-metadata">

**Author:** ![KernelPanick](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/kernelpanick/32/62_2.png) [@KernelPanick](https://forum.storj.io/u/KernelPanick)\
**Post date:** [June 1, 2024, 6:08am UTC](https://forum.storj.io/t/updates-on-test-data/26034/548 "2024-06-01T06:08:56Z")

</div>

I don’t understand the thinking behind requesting to slow the testing down. My thoughts are let my node roast. Push it to the limit. Move fast and break things. We’ll be better off when the project is ready to intake the big players. I’ll adjust and optimize.

---

<div class="post-metadata">

**Author:** ![flwstern](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/flwstern/32/7821_2.png) [@flwstern](https://forum.storj.io/u/flwstern)\
**Post date:** [June 1, 2024, 6:51am UTC](https://forum.storj.io/t/updates-on-test-data/26034/549 "2024-06-01T06:51:15Z")

</div>

My nodes are fine but you are saturating my bandwidth.

---

<div class="post-metadata">

**Author:** ![ACarneiro](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/acarneiro/32/1129_2.png) [@ACarneiro](https://forum.storj.io/u/ACarneiro)\
**Post date:** [June 1, 2024, 8:03am UTC](https://forum.storj.io/t/updates-on-test-data/26034/550 "2024-06-01T08:03:04Z")

</div>

I amuses me that after months of complaining that we don’t have enough traffic, so many people are complaining that… we have too much traffic!

Tweak your configurations to what suits your situation, reduce concurrency or bandwidth if you have none to spare or your router is struggling and be grateful that the traffic (and hopefully the money!) is flowing 🙂

---

<div class="post-metadata">

**Author:** ![ACarneiro](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/acarneiro/32/1129_2.png) [@ACarneiro](https://forum.storj.io/u/ACarneiro)\
**Post date:** [June 1, 2024, 8:05am UTC](https://forum.storj.io/t/updates-on-test-data/26034/551 "2024-06-01T08:05:14Z")

</div>

> [@flwstern](#):
>
> My nodes are fine but you are saturating my bandwidth.

That is interesting.  
I’m seeing about 40Mbit download per IP (irrespective of the number of nodes behind it). This is more or less consistent across multiple ISPs in three separate European countries.

---

<div class="post-metadata">

**Author:** ![Mitsos](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mitsos/32/1125_2.png) [@Mitsos](https://forum.storj.io/u/Mitsos)\
**Post date:** [June 1, 2024, 8:16am UTC](https://forum.storj.io/t/updates-on-test-data/26034/552 "2024-06-01T08:16:27Z")

</div>

Only about 0.5PB of (pre-expansion) data left to be uploaded, I don’t think we have anything more to worry. Should be done in a couple of weeks.

 ![Screenshot_20240601_111502](https://storj-s3.bcdn.literatehosting.net/original/3X/d/7/d76cc8583d19e1cb1494c4d216f4df02b361121d.jpeg)

---

<div class="post-metadata">

**Author:** ![JWvdV](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/jwvdv/32/7814_2.png) [@JWvdV](https://forum.storj.io/u/JWvdV)\
**Post date:** [June 1, 2024, 8:43am UTC](https://forum.storj.io/t/updates-on-test-data/26034/553 "2024-06-01T08:43:56Z")

</div>

> [@ACarneiro](#):
>
> I amuses me that after months of complaining that we don’t have enough traffic, so many people are complaining that… we have too much traffic!

Exact same feeling here.

Besides, I’ve got some really crappy nodes even existing of some very doubtful functioning SMR drives, although with enough RAM (partially artificial expanded using zram-tools). But they are far from being roasted at the moment.

However nice to see my nodes expanded 1.5TB over 10 days now. Never seen such increase before. Although, just only 1/3th coming from SLC.

---

<div class="post-metadata">

**Author:** ![jammerdan](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/jammerdan/32/1121_2.png) [@jammerdan](https://forum.storj.io/u/jammerdan)\
**Post date:** [June 1, 2024, 8:45am UTC](https://forum.storj.io/t/updates-on-test-data/26034/554 "2024-06-01T08:45:13Z")

</div>

> [@ACarneiro](#):
>
> I amuses me that after months of complaining that we don’t have enough traffic

Should’ve used the months with low traffic for testing and code optimization.

---

<div class="post-metadata">

**Author:** ![bebeo92](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/bebeo92/32/7826_2.png) [@bebeo92](https://forum.storj.io/u/bebeo92)\
**Post date:** [June 1, 2024, 9:00am UTC](https://forum.storj.io/t/updates-on-test-data/26034/555 "2024-06-01T09:00:33Z")

</div>

Hi, sorry for join the party late  
But is there any link/sum-up what we need to change to adapt with this?

I think it is fair to ask a recommendation config/tweak for node operator

---

<div class="post-metadata">

**Author:** ![agente](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/agente/32/1137_2.png) [@agente](https://forum.storj.io/u/agente)\
**Post date:** [June 1, 2024, 9:21am UTC](https://forum.storj.io/t/updates-on-test-data/26034/556 "2024-06-01T09:21:40Z")

</div>

> [@ACarneiro](#):
>
> I amuses me that after months of complaining that we don’t have enough traffic, so many people are complaining that… we have too much traffic!

He’s talking about test data that will be removed soon from nodes (ttl 30days?) with another big deletion effort.

---

<div class="post-metadata">

**Author:** ![JWvdV](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/jwvdv/32/7814_2.png) [@JWvdV](https://forum.storj.io/u/JWvdV)\
**Post date:** [June 1, 2024, 9:26am UTC](https://forum.storj.io/t/updates-on-test-data/26034/557 "2024-06-01T09:26:26Z")

</div>

> [@agente](#):
>
> He’s talking about test data that will be removed soon from nodes (ttl 30days?) with another big deletion effort.

Yeah, so, big deal?  
Or am I really missing a point?  
It’s a nice treat for the network to see if done nodes get roasted or not.

Besides, only 1/3th in my case is test data.

---

<div class="post-metadata">

**Author:** ![ACarneiro](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/acarneiro/32/1129_2.png) [@ACarneiro](https://forum.storj.io/u/ACarneiro)\
**Post date:** [June 1, 2024, 9:26am UTC](https://forum.storj.io/t/updates-on-test-data/26034/558 "2024-06-01T09:26:26Z")

</div>

My understanding was that TTL data would be just deleted without needing bloom filters so the effort will be fairly low 🙂

[Previous page](https://forum.storj.io/t/updates-on-test-data/26034.md?page=23)

[Next page](https://forum.storj.io/t/updates-on-test-data/26034.md?page=25)
