Vesa 2 LFB vs Banking

Question about which tools to use, bugs, the best way to implement a function, etc should go here. Don't forget to see if your question is answered in the wiki first! When in doubt post here.
Post Reply
pikasoo
Member
Member
Posts: 30
Joined: Sun Sep 02, 2012 11:04 am
Contact:

Vesa 2 LFB vs Banking

Post by pikasoo »

Hi,

I would like to know if some of you tested the real performance of both ...

from what i could read on diferent website, the speed was'nt always listed as a diference between lfb and banking.

i tested both on 3 emulator, bosch and microsoft virtual pc didnt realy got faster but virtualbox went on the speed, prety much 4 or 5 time faster (ex doom game went from normal fps to impossible to play) as if the emulator forgot any timing for the PIC
(btw i use the PIC for now to produce a tickcount so doom should of keep the normal fps)

so im wondering, on a real hardware, what should be the real advantage of using LFB ???

i guess that banking slow you down when you change the bank but does it realy make a huge diference?
User avatar
Brendan
Member
Member
Posts: 8561
Joined: Sat Jan 15, 2005 12:00 am
Location: At his keyboard!
Contact:

Re: Vesa 2 LFB vs Banking

Post by Brendan »

Hi,
pikasoo wrote:i guess that banking slow you down when you change the bank but does it realy make a huge diference?
Just wait until you're stuck with a 24-bpp mode and realise that one third of a pixel is in one bank and the remaining 2 thirds of the pixel are in a different bank... ;)


Cheers,

Brendan
For all things; perfection is, and will always remain, impossible to achieve in practice. However; by striving for perfection we create things that are as perfect as practically possible. Let the pursuit of perfection be our guide.
pikasoo
Member
Member
Posts: 30
Joined: Sun Sep 02, 2012 11:04 am
Contact:

Re: Vesa 2 LFB vs Banking

Post by pikasoo »

Brendan wrote: Just wait until you're stuck with a 24-bpp mode and realise that one third of a pixel is in one bank and the remaining 2 thirds of the pixel are in a different bank... ;)
It's true that 24bpp require more code specially in bank mode
User avatar
Love4Boobies
Member
Member
Posts: 2111
Joined: Fri Mar 07, 2008 5:36 pm
Location: Bucharest, Romania

Re: Vesa 2 LFB vs Banking

Post by Love4Boobies »

pikasoo wrote:I would like to know if some of you tested the real performance of both ...
Performance depends on the hardware. There is no such thing as a general performance estimate.
pikasoo wrote:i tested both on 3 emulator, bosch and microsoft virtual pc didnt realy got faster but virtualbox went on the speed, prety much 4 or 5 time faster (ex doom game went from normal fps to impossible to play) as if the emulator forgot any timing for the PIC
The timer is irrelevant as far as your problem goes so why even mention it? The game is also unplayable using a remote desktop and a slow connection or when using a computer that is 25 years old but those are also not the cause of your problem.
pikasoo wrote:(btw i use the PIC for now to produce a tickcount so doom should of keep the normal fps)
Don't confuse the PIC and the PIT. They are two very different animals. The former manages interrupts while the latter is a counter.
pikasoo wrote:so im wondering, on a real hardware, what should be the real advantage of using LFB ???

i guess that banking slow you down when you change the bank but does it realy make a huge diference?
It does make a difference because, in the case of bank switching, you sometimes waste some time mapping pages and performing address calculations. The fact that switching from one area of the screen to another requires a switch makes real-time rendering less predictable. Also, since banks may overlap, you may need to use mechanism to decide which bank to use (something like a scheduling algorithm or a preemptive hint or something).
pikasoo wrote:
Brendan wrote: Just wait until you're stuck with a 24-bpp mode and realise that one third of a pixel is in one bank and the remaining 2 thirds of the pixel are in a different bank... ;)
It's true that 24bpp require more code specially in bank mode
That's not at all what he meant. Higher depths don't imply more code. It's just that it's not elegant to plot part of a pixel and then correct it after the switching is complete. However, for banks that overlap, that's not as much of a problem...
"Computers in the future may weigh no more than 1.5 tons.", Popular Mechanics (1949)
[ Project UDI ]
Post Reply