Temp On Rez - Performance/Load Question

My object A contains object B in its Inventory. Object A script will rez several copies of object B. B objects are temporary. I see two ways to do this.

1. After developing object B, set it's Temporary attribute in the Edit interface and then Take it into object A's Inventory.

2. In object B's script, in on_rez use llSetPrimitiveParams to set the Temp On Rez. (in this case the B object would for an instant NOT be temporary).

Clearly option 1 will perform better, since the servers need to do less work (but *I* have to do more work, remembering to set the Temp flag each time I modify object B and re-take it)

My question is: Is there a significant difference for performance or server load between options 1 and 2 ?

Option 2 will increase the number of permanent prims on the parcel for a moment. If the parcel is close to the prim limit, this could be an issue. Option 1 doesn't do that.

I usually name my temporary objects to make it obvious they need to have their temporary flag set. For example, if I am working on a platform that should eventually be temporary, the one I maintain might be called "Platform 1.2 - nontemp". When I am ready to stuff it, I rez a copy, change the name to "Platform 1.2", set the temporary checkbox, and take it. Now it is obvious in my inventory that I have a permanent copy and a temporary copy. Once I throw it in the rezzer, I'll probably delete the temporary copy to be sure any changes I need to be make are made to the permanent maintained copy.

There's a Save Object Back to Object Contents (or something close to that) under the Tools menu that's very helpful for just this sorta thing..

When I do stuff like you're doing, the workflow is something like:
- make object B rez
- disable Temp on object B
- edit scripts or prims or whatever on object B
- turn Temp back on
- Tools->Save Object Back to Object Contents
- rinse, repeat

Once you get used to it, it's really not that much work - just a few mouse clicks.

Another advantage to option 1 is that if object B ends up on no-script land before it can set temp, or if the script freaks out and doesn't manage to set it, you won't end up creating litter.

It was, but it's been broken for some time

/me rummages....

http://jira.secondlife.com/browse/SVC-578 is it, maybe it needs some votes (just added one).

TY to both of you. I am already doign what HeWee suggests. I was looking for something my feeble mind would find foolproof. (Yesterday I forgot to reset the temp flag. The rezzer rezzes obj B once every few seconds at random locations, and obj B is also invisible. I left my parcel and returned to find available prims exhausted and 300+ invisible thingies floating around. Now obj B has llDie in a suicide timer in case i get stupid again).

Sindy makes an excellent point re no-script land or other anomalies. And TY for the Take Back option.

Thanks again.

It's not totally broken, though it's sometimes a little flakey - I gave the JIRA a vote anyway.

It seems to work for me if I make changes to the script of the rezzed object. Maybe not 100% of the time but more often than not.

Hey, it still wouldn't HURT to set the temporary flag from a script on rez (maybe doing it only if the start parameter is non-zero, so it doesn't happen when you rez it from your inventory to work on it). That means you have Option 1 when you do things correctly, and Option 2 if you happen to miss the step of ticking the temporary checkbox.