Odyssey 3.0 Alpha vs 1.23r5

@Maijestro


Skethblock supports extmem.

@Maijestro

Quote:
Certainly not "solved"; more like, "alleviated".

Quote:
No no no, it's actually very easy to use! I got it working in Rave without much hassle. Any developer can contact me if they'd like to give ExtMem a try.

Whether an application can benefit from ExtMem is another question. Basically, it's good for storing any data that doesn't need to be accessed at a given time, or very frequently. Like undo data, for example. Or game assets not used in the current level.

@trixie

Quote:

Is there a simple test case or test program that uses this function?

I would like to see more than the usual limited 2 GB of AmigaOS 4.1 being used. Maybe someone could write a small test program with ExtMem support.

We are straying from the actual topic, and I apologize, but Exec Extended Memory is really interesting to me, and I wanted to learn more about it.

@utri007
NetSurf? Next to useless (of course better than AWeb, and in some cases maybe even better than IBrowse), unless some huge improvements were added to it since the last time I used it.
JavaScript: Is it supported now in newer versions, and even if it is: With a PPC JIT Engine? If not: Useless.
A PPC JavaScript JIT, there were some alpha versions of it already but nothing usable yet and not included in OWB, might have been enough at the time I ported OWB to AmigaOS, about 15 years ago.
Nowadays even a PPC native JavaScript JIT wouldn't be enough anymore, you additionally need WebGL, WebAssembly, Rust, etc. support for any usable web browser.

I hope Odyssey 3.0 will be successful. Kudos to all involved.

My system is a MicroA1 with 256 MB RAM, which is a very small amount of RAM compared to the systems most other people use for OS4.

For me, Odyssey 3.0 Alpha launches, does the font thing, shows the main GUI window and eventually locks up. I got further when I changed the screenmode from 32 bit to 16 bit. I was able to display Amigans website.

For now, I will continue to use IBrowse 3.0a and Odyssey 1.23r5 and NetSurf 3.12 development test builds.

Cheers,
redfox

So how much RAM does the A600GS got?

My PowerMac with MOS got less than 2GB.

Just saying...

@hotrod
Quote:4 GB. 1 GB is used by the emulated AROS/m68k guest OS, the rest only available on the Linux/ARM host OS.
But how is that related to Odyssey in any way? AFAIK there is no AROS/m68k version of it, only x86 and x64 ones.
My more than 15 years old AmigaOS 3.9/m68k port of OWB should work on the A600GS, but probably only if you install AmigaOS 3.9 on it, very unlikely with the included AROS/m68k + SystemV46.

@joerg

AROS 68k is not compatible with OS 3.9, AROS 68k is based on OS 3.1.

OWB 3.0 is a modern, fast browser compatible with many websites, but for optimal performance it is best to have 4GB of RAM or more.

OWB 3.0 can be used on AROS x86 32-bit, but due to the RAM restrictions of 32-bit, it cannot be as fast as it is on AROS 64-bit, where you can take advantage of all the RAM of the PC hardware.

@joerg

Device running modern webbrowsers not requiering huge amount of RAM was the point here. So just my powermac then and MOS under QEMU. Done lots of browsing there and don't even have 2GB of RAM and it never runs out. With max cache on harddisks using up RAM as well.

Thought was that if it's true that it requires that much RAM it would be true everywhere regardless of device and OS and that doesn't seem to be the case.

Google Chrome run on linux pretty much so the RAM available for Linux is as much as it gets so 3GB then.

Now I'm not the time that have 20 tabs with heavy sites open but running out of RAM isn't something that I have experienced under MOS at least.

It all sounds a bit hypothetical. A bit "in windows, in windows, in windows". It's a whole different OS to begin with.

Also Odyssey, you can browse on the Wii, has mem-requirements gone up that drastically and what needs it?

Maybe ask why Wayfarer doesn't require that much RAM then.

Also, selling machines with 4GB RAM fitted, available to use 2GB let's call it freely and then *BAM* must have at least 6GB to use the most important software there is pretty much making every NG Amiga obsolete...

Why does it need 6GB of RAM under AROS 64 bit when wayfarer doesn't would perhaps be more interesting? It is VERY up to date and modern.

Or am I insulting developers now making it sound like some are better than others or something? Not my intention.

I COULD set up a VM and install a linux-distro or two and investigate and argue and what not. But wouldn't it be more interesting to know why it isn't a requirement under MOS then since it's very similar to AOS?

Also A600GS, only the GUI and a little bit of conv-code runs under emulation. The remaining 3GB RAM is for Linux and software running there from what I understand.

Under Linux there are SWAP-partitions as well... forget about that at the moment. The difference between wayfarer and odyssey then it seems.

@hotrod

Quote:

I think the short answer is that Odyssey 3 is very much an alpha. It's not even stable yet, and everything is statically compiled.
Whereas Wayfarer is (I expect) a more mature and occasionally updated product, and having made it stable, the developers were then able to move to the next level and make it elegant. Even at "elegant", both are probably still much fatter than a native solution like IBrowse, even if IBrowse were expanded with the very same modern features. Given enough development time, I expect Odyssey will take on a similar footprint as Wayfarer.

@hotrod

The mininum supported configuration for Odyssey 3.0 under AROS 64-bit is 2GB RAM. My tests show that with having 2-3 tabs opened and browsing mostly amiga-friendly sites + Discord, the RAM usage stabilized around that number.

Keep in mind that Odyssey 3.0 on AROS 64-bit is pre-configured to use larger caches as simply RAM is not a limiting factor here. Having JavaScript JIT also consumes some additional RAM, probably in the range of 0.5GB.

In order to cut the caches to minumum you can change the Cache Model setting in Odyssey preferences from "Primary Web Browser" to "Document Viewer".

Finally it is quite possible that Wayfarer has a smarter way to manage caches when memory consumpion reaches hardware limit. There is nothing stopping this from being implemented in Odyssey, because Odyssey 3.0 is using the public part of Waywarer 3.0 codebase already.