Core i7 Assigned Trial Factoring
 

I also would like to know why my Core i7 is assigned trial factoring.
I recently upgraded from a Core 2 to a Core i7 and used my old config file. It continued running the LL test on the two primes I was testing before I upgraded, but my other two cores got trial factoring test and then when one of my first cores finished their LL test it went on to trial factoring.

Now, all four of my cores are doing trial factoring. While this is helping my ranking with trial factoring considerably, i'd prefer to do LL test.

I checked my config file and it has '0' as the recommended work setting, which was what it was at previously when my Core 2 was being assigned LL test.

I don't know why it decided to automatically pick TF, but you can manually choose which type of work to receive at the web interface at [url]http://www.mersenne.org/worktype/[/url] (also see that page for the priority order for when different sources say different things for what work to hand out) or by setting the option for Prime95. If you need the number code for first-time tests, it's [CODE]WorkPreference=100[/CODE]To set all cores to that, put it at the beginning of prime.txt. To make only specific cores have that, put it under the appropriate [Worker #x] headings.

You shouldn't be getting TF unless the program miscomputed your CPU speed or you set the hours-per-day to 1 or 2. Does Options/CPU show that the CPU type and speed was detected correctly?

I've attached my CPU settings screen, which looks all in order. One thing I did notice when looking through the logs was that when I was given assignments it would make this note:

[quote]CPUs with 256K L2 cache or less will not be assigned LL tests on exponents above 20000000.[/quote]

I remember reading a post about this topic on how it counts your L2 and L3 cache, maybe it isn't doing this?

Here are the settings in my Prime95.txt:
[code]
V24OptionsConverted=1
SendAllFactorData=1
StressTester=0
UsePrimenet=1
Left=1680
Top=135
Right=2509
Bottom=873
W1=0 0 811 132 0 -1 -1 -8 -28
W2=0 132 811 264 0 -1 -1 -1 -1
Windows95Service=1
DialUp=0
V5UserID=jcmcbeth
WorkPreference=0
AskedAboutMemory=1
Priority=1
DaysOfWork=5
RunOnBattery=1
W3=0 264 811 396 0 -1 -1 -8 -28
WGUID_version=2
W4=0 396 811 528 0 -1 -1 -1 -1
W5=0 528 811 661 0 -1 -1 -1 -1
[PrimeNet]
Debug=1
ProxyHost=
ProxyUser=
ProxyPass=
ProxyMask=0
[/code]

Also, looking at this I did notice something that might be an insignificant bug that is unrelated,

[code]
Left=1680
Top=135
Right=2509
Bottom=873
[/code]

I have a dual screen setup, when I remote desktop in I can't view the Prime95 screen unless I maximize it because the window is set to show on my other monitor, and only the main monitor is displayed for remote desktop.

[QUOTE=ScrappyJoel;169221]
I remember reading a post about this topic on how it counts your L2 and L3 cache, maybe it isn't doing this?[/QUOTE]

Can you email your prime.log file to me? Thanks

I couldn't find your e-mail, what is it?

:woltman:

The L3 cache size was sent to the server properly. A PHP typo caused the get-assignment code to not use the information. You should now get LL tests.

haha finally...