nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Slow Response

ProfessorX

We have a lot of custom code on our site using asp and MS XML parser 4.0

When I put the code on the C:\ drive and point IIS to it it renders the page fairly quickly.

But when I point IIS to the Y:\default\main\.... (same code)

It takes much more time to render the page (4 fold)

Any hints?

Thanks in advance!
WIN2K TS/TST 5.5.2 sp5; OD 5.6.0.1; DD 5.5.2
The Professor-

Find more posts tagged with

Comments

Migrateduser

There's always going to be a slight performance hit doing things directly on the Y: drive, but a 4x increase sounds excessive. If the page takes long enough that you could measure it, you might try enabling throughput counters and then doing an iwstat -c to get an idea what's going on. Downloading filemon from sysinternals.com would probably be my next step after that.

If there are any profiling tools in ASP.net (if I recall correctly, it actually does profiling for you if you enable debugging), that might give you a hint as to exactly what section of the code is being impacted by the move to the Y drive.

ProfessorX

I did an response.out on the heavier part of the page.

I new it had to do wiith file objects or the like. In one part our developers program they are doing an enumierate over some directories within the website to look for images. This is the main cause of the slow down.

var folder = FileSystemObj.getFolder(path + imageFolder)
if (folderMap[folder] == null) {
var files = new Enumerator(folder.files)
var fileNames = ""
for (; !files.atEnd(); files.moveNext()) {
fileNames += files.item().name + ";"
}
folderMap[folder] = fileNames

}

Going to try and do somthing to by pass this.

Any hints

Thanks in advance!
WIN2K TS/TST 5.5.2 sp5; OD 5.6.0.1; DD 5.5.2
The Professor-

Gregg Faus

I've often thought about changing my code just so it behaves when virtualized in TeamSite, but then I usually don't because the page(s) are rarely viewed and it just a bad idea to code in Interwoven "hooks".

Knowing the context of when this code may be helpful if an alternate solution is suggested. To me, it looks like your stuck w/ the performance hit if this code is necessary.

Migrateduser

Like gfaus I wouldn't recommend recoding it just for TeamSite's sake if the page isn't going to be looked at a lot. On the other hand, iterating over a directory tree to look for files is usually a sub-optimal solution even outside of TeamSite. I would also be curious to know the context. Some ideas that come to mind off the top of my head to improve it would be to put the image paths in a database and query it, or if you wanted to keep it purely dealing with the filesystem you might be able to come up with a way to cache the results of the directory iteration in a session or application variable (of course, that only helps if you are hitting the same code repeatedly and if you have some way to keep the cache up to date).