Rolling Restart for 1.25.5, Feb 3-5 2009

uum hows it going? is it done yet?

at least the bear dispenser doesn't work any more - or I'm to stupid to use/find it...

on the topic of sculpts.

You still can not sit inside the bounding box of a sculpt.

Example : make a backdrop of mountians, hills, whatever out of a 1024X1024X100 mega prim. Try to sit on a box (that does not contain a sit target) anywhere inside the phantom mega prims bounding box. Fail.

Any chance you guys will update sim hardware to a decent spec anytime soon? Or will we just continue to dump more back end onto these weak, stressed machines?

This get's even more interesting, as I've never seen a sim falling below a time dilation or 0.5 for a longer time (except hopeless cases, where nothing helps and "0.25" is a good value). So there's not THAT much more performance required...

Update 5000 or so hardware boxes? You're seriously asking for them to do that?

I've heard LL mention class 6 hardware, though I have no idea how long it will be before we see it. I'd expect that when those go live, it will be for new sims only - mainland and existing estates aren't going to see it any time soon.

As long as we're talking about collisions, I noticed the odd behavior described in SVC-3580 had returned at the Prim Pump in ANWR when ANWR was running 1.25.4.

I'll have to take another look when it's on 1.25.5.

Maggie -- let us know.

Re: problems with megaprims : megaprims are not officially supported. When people ask "why don't you just officially support them", I would say we may have an exhibit A right here... there are assumptions built into the code, and we're not even necessarily sure what they are, that prims aren't too big. A prim that's many times larger than the area of the region... will, I guess I'm not surprised if things behave strangely around it

Wenn, Class 5 is based on a now _31_ month old CPU. I don't even know, if intel still sells it.



Would at least be a start. Xeon L5430 should do it nicely - 4 Cores, only slightly more power (50W to 40W) and a current design; so should be double the performance, if not more... I guess, there will be even some air to really *use* the current limits (100 avas, 15k prims and so on); maybe even more!

It's back to normal after the roll. This one's a real headscratcher.

With the way sims run one (or 4) per core, they'd be better with a QPI setup instead of sticking to the old FSB stuff.

There's also a line they probably won't want to cross with the number of cores per server. If they wanted to, they could stuff 16 processor cores in each sim host - 16 full regions - each with more compute power per core, but doing that would shift the bottlenecks closer to things like disk and network (and memory) than they already are. That'd also mean that a single blade failure would take down 16 sims instead of just 4. I don't know where the magic number of processor packages:cores:hosts is but just putting a faster processor in there isn't necessarily what they want.

I suspect that calculation may be a little suspect.
Here is the reported free memory from compiling the same script 6 times, with no chages.

[12:10] DanceMaster Solo V1.00: 4746
[12:11] DanceMaster Solo V1.00: 8186
[12:11] DanceMaster Solo V1.00: 4648
[12:12] DanceMaster Solo V1.00: 8196
[12:13] DanceMaster Solo V1.00: 4676
[12:14] DanceMaster Solo V1.00: 4770

Very Keynes-- can you post the source of that script?

Can someone do me a favour and give the database a hefty kick again.......tps are now multiattempt to get through again

.25 is a good value for time dilation? Maybe if you use your sim to stand around in and not much more or read too much trite propaganda from minister Zee.

---> I dont know why sims all say 22 ms of total frame time now. It used to be a useful metric to see how close you were to time dilation. Now it's solid at 22-23ms. Anyone know why? Has more overhead been routed to the limp sim hardware?

I notice the 1.25 server code sucks. It has a cyclic dilation problem. It's over stressed hardware or bad code (or both!). You get random lag storms in a fully empty sim. What gives with this?

Is there any one besides Zenity and LL who think this level of performance is acceptable?

I'm suggesting they get a plan of some sort. You suggest updating the sim hardware is not possible. They might as well turn out the lights and go home then.

If i was the boss i'd make the network code free, destroy the L$ and focus development on an IPG (internet payment gateway). Make the virtual world free to run on DECENT HARDWARE make the code free so DECENT CODERS can get their hands on it. LL should make money from being the ATM of the virtual world. Instead of focusing on being a server farm and limp theme land.

Or they can continue to milk the old cow with saggy teats until it gives it's last drop.

Well not a bad update since there is so little complains after the rollout, and people are discussing the server configuration and business model, instead of the roll-out.

Indeed

I am going to close this thread since 1.25.5 is out and happy.