Is WUG and SQL on the same server?  what version of OS and SQL are you running?  If you are runnign 2008 and SQL 2008 on the same server you may need to limit the amout of memory SQL can take. 

If the problem was WUG and SQL running on the same box then Erik would most likely have seen poor performance on version 14 as well.

We've recently upgraded from v14 to v15 and we have had exactly the same problems. The new interface is incredibly slow compared to the old. It's almost at the point of not being useable. It looks flashy but performs like a dog. The default layout is terrible as well. A lot of the screen is now taken up with empty space and there are icons all over the place.

I feel the same way, the interface is slow to load, slow to use, the column layout is terrible when changing between regular and full screen mode.

You cant use multiple subgroups if you want an overview of selective devices, it has to be the folder where the actual devices are.

Webinterface cant sort devices properly by IP, as it takes 1, 10,100 before 2,20,200 etc. While console mode this works fine.

Running a virtual 2008 R2 64bit with 8Gb ram, sqlserver 2005, and database is 1gb in size sofar.(vmware5)

cant wait until there are some improvements on the design there to speed things up a bit.

I run everything on a single box - including flow pub and the event log management suite. I have no speed issues - it is just as fast/slow as v14 was.

My box is physical - Dell PE1950 with dual Intel E5320 (total 8 cores), 16GB RAM, two 4-port intel server NICs, onboard storage with 15KSAS drives (2.5"), MS SQL2008 database and the OS is Win2K8R2 SP1.

I too performed an upgrade to v14 - and while I agree that the new web interface needs some work on design and bug removal, it is responsive; or at least just as responsive as v14 was for me.

Ok, I guess I have lost track of this issue. I am currently running 14.3.2 and initially held off on doing the v15 upgrade due to all of the complaints about performance and layout. Actually, I thought the latest release resolved most of these issues and I had not really taken the time to plan the upgrade. However, I not one to stay on back level software for long periods of time, so with that said;

Are these known issues within IPSwitch?

Are the issues being addressed? If so, how and when?

Is there a "Bug Track" site the user community can follow bug fixes? If not, please set one up!

As far as I'm concerned, I will not upgrade until the issues with V15 listed here and in other threads have been properly addressed.

Regards,

Danny

Personally I have had less issues out of v15.1 than v15 or v14.x.  The only issue I have which was the case with all previous versions is the polling engine crashing.  I know it is being looked and and in v16 the polling engine is being re-worked. 

Now it still takes time to find where everything has moved in v15 but I have not seen the slowness beign reported except when it is actually PC related and not WUG related

First of all, thank you for all of the replies.

With regard to server OS and SQL version, I'm running Windows Server 2003 Enterprise, and I have SQL Server 2005.

Everything is running on one box.

I have 8 CPU cores and 8GB of RAM and a RAID 10 disk system (directly attached storage).  The Database is a 7GB file, with 5GB of data.  From looking at Task Manager and some Performance Monitor data, the machine usually has about 5GB of free RAM.

It seems like this machine should be able to run WUG quite well.  The console application works great, no performance issues.  The web interface is quite slow and painful, however.  I haven't even mentioned any of the issues 'using' the new web interface, that may be another topic all together.

I'm just wondering, are there any IIS tweaks or any tricks which would increase the web site performance?   The client PC I'm running this on is fairly powerful too.  I'm just having trouble understanding why the web interface is so slow.

Just to rule out one last thing is the web interface even slow on the server?   I understand the console isn't but what about the web interface.  If it is I am not aware of any tweaks and not sure if support does. I did not have this issue, but we also change hardware when we upgraded and moved the SQL server off to its own clustered enviroment. 

Now if the web interface is responsive on the WUG server then I would have to say the issue is PC related or network related. 

Sorry couldn't be any more help.

Moved to the appropriate forum.

We are experiencing the same problem.  Web interfaces sometimes freezes all other web window that are open.

@WVEOC, I would recommend giving our support group a call.  They will be able to take a look at your configuration and hopefully pinpoint the cause of the issue.

Same problem here. SQL on 2008-server with Win2008 x64, WUG on other 2008 x64 server, and very slow in different browsers. Seems to be related with the amount of interfaces a device has. With 1 or 2 interfaces the problem seems to be less then when trying to get a report of a device with 10+ interfaces, such as a Fortigate router.

I have to comment here as well, the New WUG web interface engine is rediculously slow compared to the old web engine.  I think I can say what the devleopers won't , it's poorly coded and was released with bugs and will limp along until the next major release.

Follow up with a case in point.  Simply logging into the web interface takes 20-30 seconds, and it has nothing to do with my setup, that's just how the new WUG engine runs on IIS, kind of like a Delorean, Pretty but lots of junk and band aids under the hood......