Are these regions on the Main grid or Beta grid? I can find MeshTest2 on
both grids, but the server version is 13.03.04.271238, so I'm not clear
that this is the correct server version. Also TextureTest2 on beta seems to
be closed off.
On Thu, Mar 14, 2013 at 5:13 PM, Monty Brandenberg wrote:
>
Sure, it's all HTTP. But the issue as LL has been representing it, is not
that the region can't handle the traffic, it's that the clients (the
residents on their viewers) can't. I could see a blanket throttle if
Regions were the problem, maybe. But The whole point of what LL has been
doing is to l
On 3/14/2013 9:46 PM, Darien Caldwell wrote:
> As well I am not sure why scripts are being included in this at all. The
> HTTP issues as I understood were the number of http connections a viewer
> had to handle, with another factor in that mix being the particular
> router the resident uses and how
AFAIK Script -> External HTTP Server, Script -> HTTP Script Server
(llRequest*URL), and external client -> HTTP Script Server (llRequest*URL)
all use HTTP traffic in and out of the region server. Also, again AFAIK,
many objects/textures/&c. are now being sent across HTTP to the connected
viewers.
I'm curious how a script would be expected to recover from a 'flurry of
502/503' errors? If my HTTP enabled object is expecting to communicate with
my external-to-SL server, and instead receives an 503 error, all I could
see doing is to retry. So is hammering the server with retries really going
to
We now have three channels and a number of regions available for testing:
* DRTSIM-203. Normal release intended to go to Agni supporting
keepalive connections and other changes. Regions:
o TextureTest2. High texture count, no meshes, low residency
limit to prevent interference
