Log In     Register    

Help and Support
Ask a question, report a problem, request a feature...
<<  Back To Forum

100% cpu usage when stoping all torrents  

by Guest on 2026/09/25 03:30:13 AM    
I turned all seeds off by turning the number of seed slots down to 1 resulting in tixati consuming all of one cpu core and becoming laggy and download speed degrading , the cpu usage graph showed all usage being "base"
I had to restart tixati to fix this
by Guest on 2026/09/27 04:29:20 AM    
What version of Tixati and what OS? So before you turned down the number of seeding slots everything was running fine? How many seeds were running? If you run the diagnostic graph for cpu-netbase what does it look like? If you could take a picture and upload it somewhere and post a link here it would be helpful to see the graphs while this is happening. Can you repeat this?
by Guest on 2026/09/27 11:34:06 PM    
tixati 3.44 + i2pd
windows 11 24h2
1200 transfers(bunch of dead downloads) 850 seeds
yes everything was running fine for almost two months (which might be a contributing factor) before I turned the seed slots from 1000 to 1
I waited about an hour but it didn't seem like it would recover so I restarted it (even though my cpu is very fast(9950x3d))
sadly I can't seem to replicate it yet
by Guest on 2026/09/28 12:35:17 AM    
oh I forgot to add that in the cpu graph(all) the only Base(red) was visible all the other lines where on top of each other at the bottom
gotta remember to take screenshots sorry
by Guest on 2026/10/07 09:01:48 AM    
Esto es solo una suposición, pero lo que me parece es que al reducir las semillas a uno todas las conexiones que tenías también se redujeron a una y, por lo tanto, se unieron en un solo proceso. Para evitar tales problemas, primero reduce las semillas al número de hilos de proceso de tu equipo y no pasar directamente a uno.
Como dije es pura especulación por la descripción del problema.

TRANSLATION:

This is just a guess, but what I think is that by reducing the seeds to one, all the connections you had were also reduced to one, and therefore merged into a single process. To avoid such problems, first reduce the seeds to the number of process threads on your machine and don't go straight to one.
As I said, this is pure speculation based on the problem description.




This web site is powered by Super Simple Server