My A500+ GVP A530 feels so damn slow

[patrik]

@AMIGAZ:

Chech if exec.library is in fastmem with Sysinfo - the library list shows in which type of memory each library is allocated. If it is in chipmem, use FastExec to move it to fastmem.

Burst enabled for the datacache might make things slower on a 030. Burst speeds up sequential accesses and punishes non-sequential accesses and data accesses usually arent extremely sequential. This in combination with the 030s small cache..

So skip the "Cpu CACHE BURST" and just let SetPatch enable the caches as usual. It will enable both instruction and datacache for you, but only enable burst for instruction cache (instruction loading tends to be very sequential).

As others have mentioned, the more colours you use, the less chipram bandwidth will be available when say rendering graphics:
Hires/Hires Lace 2 and 4colours: 3.5MB/Sec write (max)
Hires/Hires Lace 8colours: 2.5MB/Sec write
Hires/Hires Lace 16colours: 1.5MB/Sec write

No read results, but I dont have them in my head and the A2000 is tucked away at the moment.


/Patrik

[patrik]

@mr_a500:

Both the Viper and the A530 are connected to the same bus, just at the opposite ends.

How fast/slow something feels to a person, is very relative.


/Patrik

[patrik]

@Zac67:

Cheers.


@mr_a500:

So, you're saying that expansion through the CPU slot would be the same speed as expansion through the side expansion slot?

Yes.


/Patrik

[patrik]

@AMIGAZ:

You shouldnt get more chipram when disabling the remapping, but more fastram. If the kickstart is mapped into chipram, it will be even slower than it is originally.

To see if the kickstart really is in fastram, you could use bustest and check that you get more or less the same read-speed for "bustest fast" and "bustest rom".


/Patrik