calling spawn() inside turf.New() isn't exactly ideal

ID:1129589
 
Jan 18 2013, 5:46 pm
BYOND Version:498
Operating System:Windows 7 Pro 64-bit
Web Browser:Chrome 24.0.1312.52
Applies to:Dream Maker
Status: Open
Issue hasn't been assigned a status value.
I noticed this code acts strange...

turf
    New()
        ..()
        spawn(100) testing.test(src)
        
        
var/testing/testing = new()

testing
    proc/test(t)
        for(var/turf/tt in oview(t, 1))
            world << "[tt] is done"


On a 256x256 map, you can comment out the spawn line and it will load in less than a second, uncomment out that line, and the map will literally not load for a very long time (despite calling spawn to have this happen later)

Why is the server waiting?
Jan 18 2013, 5:50 pm
Probably because you're queuing up 65536 events all at once. I'm not sure how many events it takes to annoy BYOND's scheduler, but 65536 might be it.
Jan 18 2013, 6:02 pm
In response to Murrawhip
Murrawhip wrote:
Probably because you're queuing up 65536 events all at once. I'm not sure how many events it takes to annoy BYOND's scheduler, but 65536 might be it.

Ah, I had not considered this... I think that's probably a reasonable number of events to choke on so I'll have to find some other way to do this.

I'm toying around with the idea of throttling autojoining. Not that this will even matter because I will save autojoin state data at some point.

Edit: 128x128 map was considerably faster.