Welcome, Guest. Please login or register.

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

Description:

0 Members and 1 Guest are viewing this topic.

Offline Amigaz

  • Hero Member
  • *****
  • Join Date: Feb 2004
  • Posts: 1959
  • Country: se
  • Gender: Male
    • Show only replies by Amigaz
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #14 on: February 02, 2007, 05:47:25 PM »
Quote

AmigaMance wrote:
Nice! :-)
 You can probably find more recent smart refresh patches on Aminet. They are all the same, more all less. I just use this one.


Yeah..this one seem to work nice  :-) only thing that bothers me is it's splash screen when it starts

Just started using MemOptimizer too...can you please tell me what parameters you are running it with?
-------------------------------------------------------------------
Amiga 4000T - A3640 '040
Amiga 4000 - CS MKIII
Amiga 1200 - Blizzard 1230 MKIV
Amiga 1200 - Stock
Amiga CD32 - TF360
A bunch of ol' A500's
 

Offline AmigaManceTopic starter

  • Hero Member
  • *****
  • Join Date: Apr 2005
  • Posts: 1278
    • Show only replies by AmigaMance
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #15 on: February 02, 2007, 06:18:32 PM »
.
A1200 PPC user.
 

Offline Amigaz

  • Hero Member
  • *****
  • Join Date: Feb 2004
  • Posts: 1959
  • Country: se
  • Gender: Male
    • Show only replies by Amigaz
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #16 on: February 02, 2007, 06:36:41 PM »
Quote

AmigaMance wrote:
Quote
Yeah..this one seem to work nice only thing that bothers me is it's splash screen when it starts

 No splash screen: SmartWB quiet

Quote
Just started using MemOptimizer too...can you please tell me what parameters you are running it with?

 The author provides a good command line in the docs:
Run >NIL: MemOptimizer 15 4096 1048576 20 NOCHIP NOFLUSH
 I would remove the NOCHIP option because even if you are using a gfx-card, your Chip-ram still gets accessed for some tasks.


You mean "SmartWB quiet" in it's tooltype?

Using the parameter from the docs too  :-)

Yeah, you're right about the chipram option
-------------------------------------------------------------------
Amiga 4000T - A3640 '040
Amiga 4000 - CS MKIII
Amiga 1200 - Blizzard 1230 MKIV
Amiga 1200 - Stock
Amiga CD32 - TF360
A bunch of ol' A500's
 

Offline Flashlab

  • Hero Member
  • *****
  • Join Date: Aug 2005
  • Posts: 1396
    • Show only replies by Flashlab
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #17 on: February 02, 2007, 06:56:20 PM »
Nice topic!

While I have most of the patches already I now completing my setup. I have one question about AmberRAM:

How can I change the name the Ram disk gets? It's named "RAM Disc" which slightly annoys me...
Amiga 4000D Cyberstorm PPC 060@50 604@200 SCSI 130Mb Ram G-Rex Voodoo3 PicassoIV Paloma Ariadne Delfina Lite

Online Flash version of BoulderDash: Offline...
 

Offline AmigaManceTopic starter

  • Hero Member
  • *****
  • Join Date: Apr 2005
  • Posts: 1278
    • Show only replies by AmigaMance
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #18 on: February 02, 2007, 07:08:33 PM »
.
A1200 PPC user.
 

Offline Flashlab

  • Hero Member
  • *****
  • Join Date: Aug 2005
  • Posts: 1396
    • Show only replies by Flashlab
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #19 on: February 02, 2007, 07:19:23 PM »
Thanks that worked!
Amiga 4000D Cyberstorm PPC 060@50 604@200 SCSI 130Mb Ram G-Rex Voodoo3 PicassoIV Paloma Ariadne Delfina Lite

Online Flash version of BoulderDash: Offline...
 

Offline stopthegop

  • Hero Member
  • *****
  • Join Date: Feb 2006
  • Posts: 831
    • Show only replies by stopthegop
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #20 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 mr_a500

  • Hero Member
  • *****
  • Join Date: May 2004
  • Posts: 865
    • Show only replies by mr_a500
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #21 on: February 02, 2007, 08:26:16 PM »
Quote
Load the handler to a hex editor, search for disc and replace c with k. Carefull not to touch anything else.


Ah, I see you're also into binary modifications. That's what I like about old software - if you don't like the text, just grab the old Hex editor and change it.

Offline AmigaManceTopic starter

  • Hero Member
  • *****
  • Join Date: Apr 2005
  • Posts: 1278
    • Show only replies by AmigaMance
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #22 on: February 02, 2007, 09:01:59 PM »
.
A1200 PPC user.
 

Offline cpfuture

  • Full Member
  • ***
  • Join Date: Feb 2006
  • Posts: 246
    • Show only replies by cpfuture
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #23 on: February 02, 2007, 09:21:32 PM »
Compliments to AmigaMance. Great topic! I've jotted down a couple of the suggestions and am eager to try them out this weekend.

Offline Karlos

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16867
  • Country: gb
  • Thanked: 4 times
    • Show only replies by Karlos
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #24 on: February 02, 2007, 09:37:51 PM »
Quote
Install a "smart refresh" like SmartWB. It will make you WorkBench windows faster, but it will also increase their memory usage.
NOTE: Although i have read many times that these patches are not required for gfx-card users, i'm using a BVision with the latest C-GFX update, and SmartWB gives me a noticable speed increase in window moving etc!! Could anyone give me some feedback on this?


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.
int p; // A
 

Offline stopthegop

  • Hero Member
  • *****
  • Join Date: Feb 2006
  • Posts: 831
    • Show only replies by stopthegop
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #25 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 AmigaManceTopic starter

  • Hero Member
  • *****
  • Join Date: Apr 2005
  • Posts: 1278
    • Show only replies by AmigaMance
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #26 on: February 02, 2007, 10:10:26 PM »
.
A1200 PPC user.
 

Offline Hyperspeed

  • Hero Member
  • *****
  • Join Date: Jun 2004
  • Posts: 1749
    • Show only replies by Hyperspeed
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #27 on: February 02, 2007, 10:56:26 PM »
Well I'm going to be a bit more critical here...

I would not use ANY of those patches you have listed there AmigaMance.

If you spend your day dragging Workbench windows about and fragmenting your hard disk I suppose they're great but give me the 'Official is Best' philosophy any day.

Some programs like 'Frogger' demand FBlit but then that movie player is the slowest load of crap there is anyway - better get RiVA(+GUI). Things that patch to this level invariably make your system hideously unpredictable and for very little benefit.

I burn CDs and do a lot of printing, multimedia, emulation, surfing and gaming - I need programs to get along with each other. When I do something to my hard disk I would much rather use DiskSalv (as programmed by a Commodore engineer) than use some 3rd party file system and it's wobbly utilities.

I'd say getting a decent hardware accelerator or graphics card is better than trying to dress mutton as lamb (and making the system untrustworthy at the same time).

If you don't have a GFX card then your best speedup will be by giving the ChipRAM a break. Add more FastMem, keep screen colours 6-bit or below, screenmodes to 15Khz NTSC or therabouts and scale down your icons using Iconian (stripping away any NewIcons bumf in the tooltypes).

Unless you're running a huge database or streaming video then I'm not sure dumping Fast File System is worth the hassle and risk either - particularly if you have a SCSI card with a fast hard disk or Flash drive.

I know I'm sounding like your Grandma here but Cyberpatcher, MultiCX and Executive 2.0 are the only patches I'd pay money for (the latter of which was rated 98% by Amiga Format if I remember correctly).
 

Offline adz

  • Knight of the Sock
  • Hero Member
  • *****
  • Join Date: Aug 2003
  • Posts: 2961
    • Show only replies by adz
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #28 on: February 02, 2007, 11:14:18 PM »
Quote

If you are using a 68000 or a 68020 with no fast-ram, please die.
For people who think that "Official = better" or can't edit a startup-sequence, please use windoze or something. It suits you better.


FYI, this is the point at which I stopped reading.
 

Offline AmiDude

  • Hero Member
  • *****
  • Join Date: Oct 2005
  • Posts: 903
    • Show only replies by AmiDude
Re: Guide: How to make OS3.x faster and more efficient.
« Reply #29 from previous page: February 02, 2007, 11:19:15 PM »
Hyperspeed wrote:
Quote
Well I'm going to be a bit more critical here...

I would not use ANY of those patches you have listed there AmigaMance.

If you spend your day dragging Workbench windows about and fragmenting your hard disk I suppose they're great but give me the 'Official is Best' philosophy any day.

Some programs like 'Frogger' demand FBlit but then that movie player is the slowest load of crap there is anyway - better get RiVA(+GUI). Things that patch to this level invariably make your system hideously unpredictable and for very little benefit.

I burn CDs and do a lot of printing, multimedia, emulation, surfing and gaming - I need programs to get along with each other. When I do something to my hard disk I would much rather use DiskSalv (as programmed by a Commodore engineer) than use some 3rd party file system and it's wobbly utilities.

I'd say getting a decent hardware accelerator or graphics card is better than trying to dress mutton as lamb (and making the system untrustworthy at the same time).

If you don't have a GFX card then your best speedup will be by giving the ChipRAM a break. Add more FastMem, keep screen colours 6-bit or below, screenmodes to 15Khz NTSC or therabouts and scale down your icons using Iconian (stripping away any NewIcons bumf in the tooltypes).

Unless you're running a huge database or streaming video then I'm not sure dumping Fast File System is worth the hassle and risk either - particularly if you have a SCSI card with a fast hard disk or Flash drive.


@Hyperspeed

You're right. I agree with you dude! :-D

 :pint: