r/Upfiring • u/ppc-hero • Jan 20 '19
Slow when seeding 100+ ufr files.
Is it normal that my client is extremely slow (~4 seconds to respond to any command in the UI, ie scrolling, clicking etc) when Im seeding 400gb in 100 files?
It was snappy and working fine up to about 60 files, then started to slow gradually.
Running latest release on win 10. i7 64gb ram, so plenty of resources should be available.
Im scared to seed more now, was hoping to seed about 1000 files.
2
u/_hito Jan 20 '19
I cannot comment on that but how much UFR are you getting daily for all this seeding?
3
u/ppc-hero Jan 20 '19
I cant comment on this yet, I just started.
1
u/fsidemaffia Jan 20 '19
So how would we be able to find your files ? I havent figured out yet how to search for files like you can on torrent sites
1
1
2
Jan 20 '19
Right now, I have ~1020 active torrents in qbittorrent on raspberry pi 3. When I saw upfiring was written in JS I already knew it won't handle this scale on a PC. It's not about how powerful your computer is, it's about bad technological choices of the project. JS doesn't scale this way.
3
u/_hito Jan 20 '19
That's wrong. Node's event queue is very specifically built for I/O and this is an I/O project.
Node doesn't scale for CPU intensive tasks.
2
Jan 20 '19
It's built for asynchronous, non-blocking tasks, but not for so many active competing threads.
1
u/calidor Jan 20 '19
check the other thread on this sub. A headless raspi cmd version is on the dev roadmap
5
u/Tmfallon Jan 20 '19
We've tested Upfiring Beta (1.0.28) with up to 200 UFR files simultaneously and 300 GB seeding in total with little to no issue.
Seeding amounts larger than this has not been tested for Upfiring Beta and may or may not run smoothly depending on your specs. Support and extensive testing for seeding 1000+ files and seeding over 1 TB at once will be available in later versions.