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 : Compaq -- Ignore unavailable to you. Want to Upgrade?

To: Dwight E. Karlsen who wrote (9721)	11/26/1997 10:20:00 PM
From: hpeace	Respond to of 97611

Dwight, I've never had a prob with a presario after I get passed the impossible setup.<gg> Hard drives are hard drives.cpq has the exact same thing(fast ultra-wide PCI scz2). I have apps at work that I create a mule pc for... I think I was one of the first people to use a mule. This company had a 16 hr. nitely process on a server. What I did was create 3 mules pcs. Then they didn't have all the Ultra pci wide stuff like now. Now, the mules connect straight to the 100mbit corp fddi backbone. Now, they have 2 large hd ultra pci wide scz2 and p266 or p300 chip. They are stripped of all windows junk and process in dos with mem extends. So, what you do is you do a copy down of the corp database to all three mules at one time. If your corp. database is 1 gig then it will take about 6 minutes to copy down. I begin processing the normal ERP batch on one of the mules. I begin extracting data that is static that the nitely batch will not change on the other two mules. then when the nitely batch finishes I start extracting on that mule too after I copy the database back up to the server. All three(mules) are designed to finish at about the same time. Then I copy up the ERP batch that finished since the factory has been locked out of that system while this is going on. So, the factory cannot do data entry for 6(copy down) + 17(nitely batch) + 6(copy back up) = 29 minutes. Then I start running all the reports in another invention called the client task processer. After I finish the three parallel processes on the mules. I create one database that is the bible. I copy that to the two other mules. On one of the mules I start a tape backup. This way it doesn't effect response times of the factory. On the other database the client task processer starts waking up a series of maybe ten pc's all over the plant. they are the most powerful pcs in the compnay. They have that pc start a job, and I have 10 jobs going at once... When a job finishes then it just picks the next one up. But, I've taken the 3 parallel processes and now have ten parallel processes. So, the 16 hr nitely process where the factory was locked out 3-4 hrs was reduced to 2 hr's and 45 minutes and the factory locked out 29 minutes. The company had 3 shifts of operators. This allowed us to do away with the third shift and have 2nd shift come in at 1pm instead of 3-4 PM. An example of JIT in computer operations. If the factory has to bust there gut and reduce cycle times and operate under TQM and JIT. The MIS should have to do the same thing. So, i'm not against faster hard drives...<ggg> A freind wanted a copy of this to compress his batch cycle times , so that's why this is here.