Welcome, Guest. Please login or register.

Author Topic: Guide: How to make OS3.x faster and more efficient. (Updated)  (Read 24825 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline stopthegop

  • Hero Member
  • *****
  • Join Date: Feb 2006
  • Posts: 831
    • Show all replies
Re: Guide: How to make OS3.x faster and more efficient.
« on: February 02, 2007, 08:15:46 PM »
I have one other to add to your list:

wballocfast >NIL:

works wonders, and I've found it to be very system friendly.
Primary:
A4000T. Phase5 PPC604e-233mhz/060-66mhz. Mediator, Z3 Fastlane, Voodoo5, Delfina, X-Surf, AD516, Peggy Plus.

Collection:
A4000D, A1200, A500, Milan060 (Atari clone), Atari MegaSTE, Atari TT030, C64, C128, Mattel Aquarius, (2) HP Jornada....
 

Offline stopthegop

  • Hero Member
  • *****
  • Join Date: Feb 2006
  • Posts: 831
    • Show all replies
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #1 on: February 02, 2007, 09:48:44 PM »
Quote
In theory, on a good graphics card the graphics.library rendering functions are hardware accelerated so that simple refresh operations ought to be fast enough so that you never see them.
There are several problems with this postulate:

1) The time it takes the system to physically set up the drawing (GUI layout etc) is totally unrelated to the speed of the underlying hardware.

2) Good hardware is often let down by abysmal drivers and the pretty hacky way RTG is implemented. A lot of acceleration is missed out. BlitBitMapScale() for example is totally software driven on my BVision under CGX4.2 except when the scale is 1:1, despite the fact the permedia can handle scaled blitting no problem. For those functions that are actually hardware accelerated, the time it takes to reach them from the graphics.library calls usually dwarves the time it takes to perform the actual operation.

Smart refresh is based around simply blitting away the hidden areas of a surface and then restoring them when they become visible again. This uses more video ram but can be achieved in a couple of blits at most. Therefore it's always going to win where (1) and (2) are significant.



I'm not sure I followed all that..?  In english: Is SmartWB a good thing or a bad thing?
Primary:
A4000T. Phase5 PPC604e-233mhz/060-66mhz. Mediator, Z3 Fastlane, Voodoo5, Delfina, X-Surf, AD516, Peggy Plus.

Collection:
A4000D, A1200, A500, Milan060 (Atari clone), Atari MegaSTE, Atari TT030, C64, C128, Mattel Aquarius, (2) HP Jornada....
 

Offline stopthegop

  • Hero Member
  • *****
  • Join Date: Feb 2006
  • Posts: 831
    • Show all replies
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #2 on: February 03, 2007, 12:28:38 AM »
Not all patches are bad, some work quite well and are very system friendly.  AmigaMance's point was to highlight the good ones.  He also warned people away from the bad ones, primarily by omission.  This isn't a simplistic clash of ideologies here("official" vs. "hack").   By all means, upgrade your hardware as much as possible and use the best (not necessarily the "latest") drivers.  But also take advantage of some really great ingenius little programs (or "hacks", if you prefer) that people have written specifically to overcome many of the shortcomings in the products that have the blessings of officialdom.    
Primary:
A4000T. Phase5 PPC604e-233mhz/060-66mhz. Mediator, Z3 Fastlane, Voodoo5, Delfina, X-Surf, AD516, Peggy Plus.

Collection:
A4000D, A1200, A500, Milan060 (Atari clone), Atari MegaSTE, Atari TT030, C64, C128, Mattel Aquarius, (2) HP Jornada....
 

Offline stopthegop

  • Hero Member
  • *****
  • Join Date: Feb 2006
  • Posts: 831
    • Show all replies
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #3 on: February 03, 2007, 01:28:10 AM »
Quote
Like stated before: If you wanna make OS3.x faster and more efficient, use a more powerfull accelerator card and/or GFX-card and/or more Fast RAM. That should do
the trick really efficient.


I've never heard anyone say their Amiga was too fast.  

 :pint:
Primary:
A4000T. Phase5 PPC604e-233mhz/060-66mhz. Mediator, Z3 Fastlane, Voodoo5, Delfina, X-Surf, AD516, Peggy Plus.

Collection:
A4000D, A1200, A500, Milan060 (Atari clone), Atari MegaSTE, Atari TT030, C64, C128, Mattel Aquarius, (2) HP Jornada....
 

Offline stopthegop

  • Hero Member
  • *****
  • Join Date: Feb 2006
  • Posts: 831
    • Show all replies
Re: Guide: How to make OS3.x faster and more efficient. (Updated)
« Reply #4 on: February 27, 2007, 06:46:00 AM »
Only problem I've had with WBallocFast is it refusing to work under DOpus.  I think this is a fault with DOpus though.  
Primary:
A4000T. Phase5 PPC604e-233mhz/060-66mhz. Mediator, Z3 Fastlane, Voodoo5, Delfina, X-Surf, AD516, Peggy Plus.

Collection:
A4000D, A1200, A500, Milan060 (Atari clone), Atari MegaSTE, Atari TT030, C64, C128, Mattel Aquarius, (2) HP Jornada....
 

Offline stopthegop

  • Hero Member
  • *****
  • Join Date: Feb 2006
  • Posts: 831
    • Show all replies
Re: Guide: How to make OS3.x faster and more efficient. (Updated)
« Reply #5 on: May 27, 2007, 04:53:21 PM »
X-Panel is a nice little tool.  
Primary:
A4000T. Phase5 PPC604e-233mhz/060-66mhz. Mediator, Z3 Fastlane, Voodoo5, Delfina, X-Surf, AD516, Peggy Plus.

Collection:
A4000D, A1200, A500, Milan060 (Atari clone), Atari MegaSTE, Atari TT030, C64, C128, Mattel Aquarius, (2) HP Jornada....