Transcom.uk Nominet pipelining ? Catches greatly improved

[Transcom ISP]

Under RFC 4930 , it says the below, anyone know if Nominet allow EPP server allows it ?

- The transport mapping MUST explicitly allow or prohibit
pipelining.

Pipelining, also known as command streaming, is when a client sends
multiple commands to a server without waiting for each corresponding
response. After sending the commands, the client waits for the
responses to arrive in the order corresponding to the completed
commands. Performance gains can sometimes be realized with
pipelining, especially with high-latency transports, but there are
additional considerations associated with defining a transport
mapping that supports pipelining:

- Commands MUST be processed independent of each other.

- Depending on the transport, pipelining MAY be possible in the form
of sending a complete session in a well-defined "batch".

 

[webber]

This is detailed in Nominet's documentation

 

[Transcom ISP]

Thanks, but I couldnt see it, Ill check again..

 

[webber]

I can't find it mentioned for EPP, but the same applies:

Queries can be sent to the real time DAC without waiting for the previous query to return. The real time DAC will just queue the queries.

 

[Transcom ISP]

Thanks, but thats for the DAC not the EPP.

On testing, one write is spot on, more than one write changes pre drop time in ms , which seems to indicate that one has to finish before the other starts, even on non blocking sockets (if they allow that even...)

 

[ukbackorder]

You can send multiple requests in one. However their load balancing and processing means there will still be a delay between the first and second getting processed. Nobody should be waiting for a response anyway - that can be checked later.

 

[Transcom ISP]

thats the odd thing, responses are ignored until after the writes, and all the writes go.without issue.

but, on one write, its xx ms (and accurate) , but on two writes it changes the first write delay, without reading anything.

(BTW write processing between seems to be fixed at about 0.5 ms)

 

[ukbackorder]

Just so you know some people are most likely (deliberately) flooding the EPP so requests have to go 100ms or more early now for some domains. I'm sure as nominet said that's 'working as intended' So I wouldn't get fixated on your delays. However if you want to join in just make sure you send 5 non-AUP EPP commands along with every 1 create and maybe when nominet get round to processing your batch of 6 yours could be the one picked. That's just a theory of course that was being bounced around.