Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Citrix Systems (CTXS) -- Ignore unavailable to you. Want to Upgrade?

To: Roger A. Babb who wrote (5242)	3/13/1998 1:52:00 PM
From: Jon Tara	Respond to of 9068

Roger, that's exactly what I meant to say. ;) I think that the applications that will work well on Winframe are the typical client-server transactional applications. Say, you've got a phone representative with a tube in front of them. Every 5 minutes or so, they plink a few keys to bring up a customer record. The server doesn't have to do a whole lot, probably passing-off the database request to a dedicated database server. The per-user load in this type of application is quite low. And, as Roger says, the existence of a market big enough to keep CTXS growing is debatable. I think it hinges on the acceptance of Winterms. If Microsoft does get their act together on remote administration, it may be moot. I am already seeing companies abandon Java strategies, and expect more of that. The question is where do they go after abandoning Java? Back to Windows-based client-server, or to server-based web applications? XML provides yet another alternative (which can involve Java or not) which could be "the answer" or another blind alley. Winframe provides ONE alternative which has the advantage of not requiring companies to step out onto a unknown ledge.

To: Roger A. Babb who wrote (5242)	3/13/1998 2:24:00 PM
From: MikeM54321	Respond to of 9068

>Mike, server loading (not LAN loading) is the problem with apps like Excel on Winframe. Even a top of the line Pentium Pro server can be brought to its knees by a couple of "power users" with big spread sheet recalcs or data base queries. And then the secretary trying to type in Word screams and throws things when the power users cause key and mouse lag in her app.< Roger, Oh! I finally get it. Maybe this is what Jon was talking about too? Now you have got a good point. I do tie up my 233mhz Pentium II/80megs of Ram with a search of my 6,000 or so sales leads in my Access95 database. It does take about 5 seconds to have the results returned on fairly simple queries. If I'm running Powerpoint, forget it! Others can't use the server while I give a presentation. So you are saying multiply this by 20 users and you have a problem! Boy did it take me a long time to get this. Thanks. So that's is what all the load balancing fuss is about. Hmm...hard one for Citrix to overcome for processor intensive applications. So this is why Citrix only says put 20 users on a server as a general rule. They may want to throw in "...and only one Powerpoint user." Now it makes perfectly good sense. And Microsoft revels in creating huge, bulkly, processor intensive applications, don't they. Well thanks to you and Jon for the education. I'm sure others learned a lot too. MikeM(From Florida)

To: Roger A. Babb who wrote (5242)	3/15/1998 12:24:00 PM
From: Al Chechatka	Read Replies (1) \| Respond to of 9068

Roger, Apps that are CPU intensive will bog down any machine, but the hooks that are being put into Winframe and now Terminal Server help get rid of this problem. For example, the thread running the Access lookup on a regular machine will bog down the whole machine, but Winframe and Terminal Server is shouldn't be as bad because they change the Thread Priority (any time critical threads now run at psuedo time critical). The multiuser interface gets real time critical. So the access app will take longer to execute on a Winframe, Terminal Server frame, because it doesn't get the full CPU cycles. This is so other apps can run even with a big app taking much of the CPU. Also, a person typing using their Word document gets a terminal I/O boost from the Kernel. So typing will not be delayed for that person. Al C.