Has it every occurred to you that a more robust solution might bring some stability and performance benefits. Have you looked at using Oracle for instance.”

For what it’s worth, Krista, we are quite aware of other database options, and of the impact of database engines on scalability and reliability. The issues of scalability and reliability are being addressed with architecture changes that are already in motion (not completed yet, but already progressing), and frankly whether the back-end database is mySQL or Oracle or some other database engine has little to do with the effectiveness of changes that need to happen to improve on those two key areas in the Second Life environment. It is always tempting to think “if only we replace this one piece of hardware or software it will all be better”, but in the large systems arena this is rarely the case.

Let’s please leave the mySQL discussion alone please, or I will start to remove iff-topic posts, as continuing this part of the discussion is way off topic for the Havok4 beta test process.

We are purposefully *not* adding features, other than revamped linkability rules, to this release, and instead working to have this be hard to crash and support existing content with minimal breakage.

Regards,

Sidewinder

My testing has shown me that this is not true AT ALL.

In fact unless the Havok beta grid is running on Class 3 machines Im finding it to be the same or much SLOWER in some instances that Havok 1 on my own sim.

While Havok 4 may be less crash prone is has not shown me that it is any less CPU intensive. A simple 11 object collision in a small slace STILL slowns the sim down to 0.3 TD.

I can’t find even one instance of my own experience in the beta grid that would support a single thing you said in your post. Things like 7000 prim link limits or > 30-40 meter link limits are certainly NOT going to be raised on realase, even if they might be in some far off future date. The limits that are there now are more because of limits in the archetecture of the mechanics of sim crossing which are not changing.

What you are talking about may be things that happen some years from now, but defintaly NOT with the upcomng release of Havok 4…

Hi Bay,

I’ll try to make this clearer… We have a production viewer - the released one that is the main download on the Second Life web site. We also at some times have a “First Look”, which is a beta of an upcoming public release. It is not release yet, and is still being worked on. Project such as our Havok4 project sync up to the *released* viewer code every couple of weeks to pick up changes. We purposefully do not sync to unreleased beta code so that we are not chasing unresolved bugs in the non-released viewer codeline. Does this help?

Thanks for asking,

Sidewinder

Has it every occurred to you that a more robust solution might bring some stability and performance benefits. Have you looked at using Oracle for instance.

I think it’s wonderful that we are allowed to test new features, and can do so in both Beta and Main grid, but i think it’s a good idea to make things less confusing

Keep up the good work¨tho

Pfffpppbbttllrrrttffftttttt.

i havent had it that bad, but some friends had it pretty bad, and lost thousand of items in a sudden.

people pay for their objects, and inventory loss makes them lose it, and no refund, and filing a ticket, takes ages, probably a year or something.

@ 19 Gwyneth Llewelyn
you cant link 7000 prims, it still holds the 254 prim link limit.