From: Krzysztof B. <kb...@un...> - 2017-01-17 21:57:05
|
Hi Sander, W dniu 16.01.2017 o 08:47, Sander Apweiler pisze: > Good morning, > > I recognised a longer response time if I browse to unity with remote > IdPs loaded from eduGain Metadata file. Last week I had some time to > investigate this "problem". Instance with eduGain IdPs has response > times between five and ten seconds. > > I investigated the communication with network tools from browser. The > POST call, where the browser sends some client information, causes this > delay. Some further investigation with tcpdump and wireshark at server > site shows that there is only traffic between client (browser) and > server (unity). Unity sends some keepalive packages. > > The long response time is on both instances with eduGain IdPs. There is > no delay on two instances without eduGain IdPs. But activating DFN IdPs > (loaded from metadata file) on one of them let increase the time for > POST method from 40ms to 400ms. > > Are there some Options to speed up the server? > Looked a bit into it. Unfortunately during authN UI preparation, there are two operations performed, both are roughly speaking of O(n^2) complexity, where n is the number of configured IdPs. As eduGain has ca 2100 IdPs it gets in fact way too slow. I've opened a ticket to track this with more details, we will need some rather complicated caching to have proper speed. https://app.assembla.com/spaces/unity-public/tickets/580 Let's move this thread to the ticket. Best, Krzysztof |