Archive of UserLand's first discussion group, started October 5, 1998.
Re: Scalability of F6
Author: erik Posted: 4/30/1999; 11:23:50 AM Topic: Scalability of F6 Msg #: 5472 (In response to 5263) Prev/Next: 5471 / 5473
Since no information is forthcoming on Frontier v6 performance, I'm going to make some wild guesses. Hopefully that will prompt some useful discussion or more information.I assume my.userland.com is provided dynamically to each user and not from a static file that is written out. That's how my personalized portal demo is served.
My guess based on what I am seeing is that Frontier on an old Pentium 150/128MB/NT4.0 with a fabulously great network connection (I'm not far from the Palo Alto Internet eXchange), is that it can only handle a dozen users of a service like my.userland.com (and the same machine is also scavenging through news sources looking for updates every hour).
I see that many my.userland.com sources are updated around the turn of the hour. Many of them seem to have a timestamp of :01 past the hour. I infer from this that the update process runs through most of the info sources within a few minutes. If so, then this is excellent performance and much better than I am seeing. You guys probably have a much faster machine than I do. One other explanation might be that most of the my.userland services do not have lots of updates every hour so perhaps you are looking at a last-updated timestamp and skipping by the source when there are no changes. (What is that column named "reads" in the select my news page of my.userland.com anyhow?) Do you guys compare every new story against your existing inventory of stories?
I find that the process of parsing pages for news stories chews up 100% of available CPU time on my Pentium 150. Typically it takes this system 15 minutes to run through 40 news services and add say 50 new stories. However they are not all RDF based, only a few are, so perhaps using the tagExtractionKit to examine headlines causes greater CPU utilization than doing a compileXML.
Is there a big performance hit from running IIS side by side with Frontier? I typically have no activity on the IIS side, but don't want to disable serving up static documents with ASP.
thanks--erik goetze
This page was archived on 6/13/2001; 4:49:39 PM.
© Copyright 1998-2001 UserLand Software, Inc.