If i compare my CPU Time of a work package with that, the other one took for this, it seems much heigher.
One example:
Package 2110388662 took my PC 4,235.58 sek with an Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz
the same package took another 63.27 sek with an Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz

there is no way, his CPU is 70 times faster than mine.
The other thing is, the tasks i instantly got at the beginning were so much, that i won't be done with them even close until the expiry date. I got even more day two, so that i didn't allowed more tasts. Is there something off with my PC or can that be normal? I my run it 10 hours a day and something do other things on it. Is it calculated like that you get as much tasks as you theoretically can handly in time, when your PC works 100% time a day with full capacity? Maybe these two things are corellated.

Maybe any ideas?

Thx, Philipp

If i compare my CPU Time of a work package with that, the other one took for this, it seems much heigher.
One example:
Package 2110388662 took my PC 4,235.58 sek with an Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz
the same package took another 63.27 sek with an Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz

there is no way, his CPU is 70 times faster than mine.
The other thing is, the tasks i instantly got at the beginning were so much, that i won't be done with them even close until the expiry date. I got even more day two, so that i didn't allowed more tasts. Is there something off with my PC or can that be normal? I my run it 10 hours a day and something do other things on it. Is it calculated like that you get as much tasks as you theoretically can handly in time, when your PC works 100% time a day with full capacity? Maybe these two things are corellated.

Maybe any ideas?

Thx, Philipp

Easy answer is his I7 has 8 cores and your I5 only has 4 cores...the cpu tasks here use all the cpu cores for each task and he's using upto twice as many cores as you are. A more in depth answer could also include him using faster memory and perhaps an ssd drive so his writes don't use as much cpu time either. But there are other factors too ie does the task fit into L2 or L3 cache, the I7 can have bigger and more of each, or is the task always swapping out to the hard drive as it goes thru it's stuff. Another could be are you also running a gpu task at the same time and not leaving a cpu core free just for it and he is, if so then your gpu could be taking time away from crunching while his isn't. The other thing that could affect it is the actual task itself, are you comparing apples to apples or is there an orange in the mix. And then there's always the 'boinc only machine' compared to your machine that's used for other stuff while crunching. ie I'm typing this on a laptop while it's crunching using both the cpu and the gpu so those tasks are running slightly slower than they were while I was sleeping.

I have 6 cores (12 Threads) CPU and a SSD. Maybe there is some thime where the SSD is the bottleneck, but i mostly see CPU at 100%, where BOINC takes around 90% from it, if i do something and the SSD doesn't have to do much most of the time and only jumps up to around 3% usage. So 70 times faster seems a lot for me, but there are other, whose have similar times with similar hardware, so there seems nothing wrong with my hardware. This large time difference still wonders me, though.

I have 6 cores (12 Threads) CPU and a SSD. Maybe there is some thime where the SSD is the bottleneck, but i mostly see CPU at 100%, where BOINC takes around 90% from it, if i do something and the SSD doesn't have to do much most of the time and only jumps up to around 3% usage. So 70 times faster seems a lot for me, but there are other, whose have similar times with similar hardware, so there seems nothing wrong with my hardware. This large time difference still wonders me, though.

Are you running all 12 threads on a single task? If so that also could be the problem, trying cutting back to one less or even try using only the 6 real cores and see if that's faster, different machines react differently to the different ways of running them.