DonPedro wrote:it is the chipset that provides the 133mhz setting. afaik the m599lmr uses the sis530, so the only thing you got to know is how to set the jumpers for selecting the various fsb/sdram speeds (100, 112, 124, 133). whether the pcchips board can stand it is a question of manufacturing quality.
I may have to try updating the BIOS then. The m599lmr has an early version of the AMI CPU PnP Setup util. There aren't any jumpers. It's only listing 60, 66, 75, 83, 95, & 100Mhz right now. Multipliers are 1.5-5.5, but I figure the 2x would work as a 6x.
DonPedro wrote:in most cases you won't succeed with onboard-vga enabled. only super7dude who has a ga-5smm was able to run the board at 133mhz with onboard-vga enabled. all others who tried it failed.
Yeah, that's why I installed the ATI card. Also, since it steals main memory, the PCI card will help allow more RAM to be available. I may try dropping it down to 64MB and see if it will still encode properly.
DonPedro wrote:you wrote: "Using the Celeron Mobile(P4 based) which has 256k L2 isn't really any slower than the P4's 512k cache." if these cpus have the same core and only differ in cache-size than I would say that this hints towards mencoder's data to be worked with fits almost into 256k cache.
There are probably some kind of differences in the way the cache is use(4way vs 8way) or something. The regular P4 based Celerons only have 128k L2. Plus, the mobiles overclock a whole lot better than the regular ones. I don't have any available to test tho. I'm building a dual Xeon system which will allow hyperthreading on both cpus, which will allow me to encode 4 streams at a time if I want to. I may grab a K6-2+ and see if it works similar with the 128k L2 vs the 256k L2 at the same speed. That would probably be the best bet.
DonPedro wrote:so far our bench adventure has revealed that programs which rely only on raw cpu-power show no improvement when one switches from 6x100 to 4.5x133. cpu and ondie-cache are both run at 600mhz. the results are equal. just look at the many charts we have produced so far earlier in this thread. the benches that have grey background will show this effect.
Correct, but mencoder is a streaming app that needs new data on a constant basis. It's not like some programs that only need to work on a small amount of data at a time. That's why the 133fsb makes such a difference. The faster you can feed it the better the results. Also, it has to push the data out. re-encoding a movie at these speeds can take a long time(about a full day for a 2hr movie). I don't really intend to do much encoding with this system. It was more of a test. Anyway, in some situations, the fsb is probably irrelevant once the data is loaded into the cpu. Depends on the program.