Maratis forum - Question: How many Tri's (roughly) can maratis handle?

Re: Question: How many Tri's (roughly) can maratis handle?

2012-02-27T12:14:17Z

I found the board and had a quick look at the translation. Looks very impressive, I mean, clearly there are much much prettier renders of that scene, but people were quoting times from 11s to 1h20m from what I could see... so considering this is realtime... it's pretty damned impressive. Maybe you have found a new market for Maratis?

Re: Question: How many Tri's (roughly) can maratis handle?

2012-02-26T10:03:39Z

I found on google image, I think it's a japanese website so I don't understand anything, but it seems they compare different rendering engines (not real time expect for Maratis). The scene looks very high in triangles.

Re: Question: How many Tri's (roughly) can maratis handle?

2012-02-25T20:30:47Z

Nice, where did you find that?

Re: Question: How many Tri's (roughly) can maratis handle?

2012-02-25T20:27:07Z

Just found on the net, someone using Maratis as a renderer :

Nistur edit: update image URL as original one expired

Re: Question: How many Tri's (roughly) can maratis handle?

2012-01-25T00:22:30Z

I will have to have a closer look at the memory, I've been a bit busy tonight unfortunately. I do know that often applications preallocate a larger amount of memory than they need. I will do it after I've finished the little changes I've done to the package manager.

But yes, it's Windows 7 x64 on both machines I've tried it on.

I might try to do the profiler at the weekend, I am interested what it might come up with. I will have to see if I can mark memory on the stack as well as the heap. If you would prefer the code not submitted I will keep it locally.

Re: Question: How many Tri's (roughly) can maratis handle?

2012-01-24T23:43:41Z

strange... is it on windows ? windows 7 ? (I only have xp)
on macosx, there is something called inactive memory, when debugging memory xcode show that the memoy used is 32mb, but the monitor shows 100mb (active+inactive). Is it like that with win 7 ?

Re: Question: How many Tri's (roughly) can maratis handle?

2012-01-24T22:09:50Z

I had a go with 2 versions of Maratis, the first being built with Visual Studio from svn, the second being the precompiled download, both have similar results. The download went up to 89MB with YoFrankie, the svn version stopped at 74MB strangely.

Re: Question: How many Tri's (roughly) can maratis handle?

2012-01-24T20:23:14Z

you was right for the sleep, it put the cpu usage down.

Re: Question: How many Tri's (roughly) can maratis handle?

2012-01-24T19:32:40Z

is it not working also when exporting from Blender ?
(at least a good point for Maratis)

I tried to load YoFrankie when packaged, and the memory seems to react approximately the same, from 10 to 32 to 10, without bigger picks than the unpacked one. Good to see

Re: Question: How many Tri's (roughly) can maratis handle?

2012-01-24T19:21:47Z

I'll send myself the mech mesh and do some tests at home. I wasn't using any profiler to get the numbers, I just glanced at windows task manager.

It's unfortunate that I can't seem to load the mech into unity, no matter how hard I try

Re: Question: How many Tri's (roughly) can maratis handle?

2012-01-24T19:16:01Z

I'm curious to see more of the comparison and test with big meshs and maybe unity. I also would like to be sure about what is happening with the used memory you recorded.

To check the svn version, I ran it with xcode and debug instruments, and opened/closed YoFrankie example,
Maratis was using 10mb at start > 32mb with YoFrankie, it came back at 10mb when closed.
The instruments recorded 4 leaks, basically 192bytes from Maratis and 400bytes from Bullet physics.

There is maybe some leak linked with the big mesh you use but I don't understand...

Re: Question: How many Tri's (roughly) can maratis handle?

2012-01-24T18:32:56Z

I will try and do some benchmark tests with the mech mesh and svn revisions, unless you have an archive of previous builds I can use.

If there's anything more detailed you want, I can quickly plug in either memory or CPU profilers I recommended within a matter of hours to get a quick reading on what sort of things are heaviest. I was just suggesting wrapping it up nicely so it could be used by others in future.

Re: Question: How many Tri's (roughly) can maratis handle?

2012-01-24T18:26:29Z

In the short term what we need most is at least a global check of the memory using an existing debugger/profiler, there is some ready made and visual tools, what I mean is we should spend the energy to do some investigation first. I don't think there is huge leaks as it was checked for the previous release, but it's a long time it has not been made.

Also, doing benchmarks like you did with the big mesh is very important.

Re: Question: How many Tri's (roughly) can maratis handle?

2012-01-24T16:21:27Z

I have checked that there is nothing apart from the box.mesh in the meshs/ directory. I have no idea what's happening :S

There are some tools on various platforms that will allow you to do CPU/memory profiling, but very few are cross platform and will allow for Maratis users to optimise their games properly. Not sure if that's important to you. What I was thinking is that we can add a MProfilerContext to MEngine, and then create macros to do something like the following:

#define M_FUNCTION_PROFILE() \
MProfileStack func(__FILE__, __FUNCTION__);

Which will wrap up checking if there's a profile plugin attached and will release at the end of the scope. I actually had a look at profilers before and Shiny Profiler looks nice and simple to make into a plugin

With regards to memory management, it would probably be a bit more hassle as it means overriding new/delete globally so you can keep track of the memory yourself. Not as painful as my fopen hack as C/C++ will allow overriding them but that can tie into the MProfileStack again, then you can print out the memory as it's been saved, with the file and function it was allocated in. Of course you don't want to have either of these things running in a production build, but if they're wrapped in a plugin, will allow projects to test what's happening, and the MProfileStack class should take minimal overhead if there's no profiler. Can even create a FinalRelease player build which defines M_FUNCTION_PROFILE in the build process, so it's not even implemented.

EDIT: I had a quick look at memory profiling, and found this which basically explains what I mean, but if we have the MProfileStack, we can actually point out when and where the allocation came from

Re: Question: How many Tri's (roughly) can maratis handle?

2012-01-24T16:03:37Z

You said you used Sponza camera, is there a chance that the sponza mesh was still in memory ?
The website release of Maratis with Yo-frankie demo opened uses 36mo (I don't have a svn build where i am)

Some memory test would be very nice to do, there is not some build-in tools to debug it ? (I use one with xcode, but i don't know if it exist with visual or on linux)