Dear fellow admins,   We are in the process of migrating a number of departments from their own dedicated SAS server to a large common grid based environment. This has resulted in a larger consolidated set of metadata that is now being served by a cluster of 4 metadata server nodes. Everything on the server side is Linux based. These servers have lots of memory and CPU load is never high. The nodes talk to each other over a 10GB connection.   We see an increase in the startup time of management console that seems to be proportional to the volume of metadata but also very dependent upon network conditions. Users that are connected via a VDI (virtual desktop) are the lucky ones: 64 seconds before getting control over the interface. Worst of are the Wifi users (also the majority) with 145 seconds. No wonder people start complaining.   We have done a network trace and see a large amount (130k) of relatively small (avg. 470 bytes) number of tcp packages. So it makes sense that network latency is our worst enemy. Total volume is not much (58MB) but is being delivered in very small chunks.   I was wondering if we are the only ones that see this and, if not, how this can be dealt with. We will shortly contact SAS Support as well but I was wondering what's happening in the field.    So, any experiences you would like to share?   Many thanks in advance, -- Jan. ... View more