Posted by Bruno Biancucci on May 09, 2006 at 13:25:34:
Here's one that just does not compute. Anyone come across this type of problem?
One Windows98se computer (finally) had to be replaced with a new computer XPproSp2 P4 system. New hardware, but I think the hard drive was kept and upgraded to XpProSp2. Comet is really slow with creating local (c:\comet\loc) temp files. Typical screen stuff (customer/inventory lookps and changes) are fine. Also, there is a printer connected on this workstation and print jobs also slow things down. My guess at this point is the printing is related to the file slowdown - fix the file issue and printing will be fine as well. Any idea's?
We've done the following to no avail.
Installation Details:
- 10 comet2005 Licenses and 10CometAnywhere licences.
- 10/100 3com switch & 100mbit nic on problem pc.
- Bunch of older Windows98se PC's
- Windows 2000server w/25Cals (comet 2005 server)
- Hardware is server class (1 gig ram, 120gig mirrored)
- Comet2005 Build .358/06.06
- CometWorkstation 358
- All Comet pc's are on the same local lan
Computer in Question:
New P4 512ram XpProSp2. If I run CometAnywhere on this computer, it's super fast (80000 record sort lookup takes 3-5 seconds). Comet on same box takes almost a minute to perform same task. We only seem to get slow down when a local temp file is created. All other tasks seem to be fine.
At the Hardware/OS level, we've looked for CPU/Memory/Network bottle necks and there were non. We can move 10meg files from workstation to/from server in the blink of an eye. The sort file being created in the comet app is about 140k. We also attached a laptop, installed comet and still got slow performance (just to make sure it wasn't THAT computer specifically). Did all the typicall pc stuff too (windows updates, check disk, defrag, repair the nic).
We Uninstalled/Installed same CometWorkstation358 and even the most recent version - same results.
There is also a mapped network drive to Comet server (Q:) that we make use of, but the comet.ini uses the UNC namings.
Following are comet.ini details of relevence:
Server = N01,TCP,L,192.168.0.2;
[DIRECTORIES]
000 = S ,\\COMETSERVER\COMET\REL\;
001 = S ,\\COMETSERVER\COMET\UTL\;
002 = S ,\\COMETSERVER\COMET\RAM\;
003 = S ,\\COMETSERVER\COMET\SRC\;
004 = S ,\\COMETSERVER\COMET\CED\;
005 = S ,\\COMETSERVER\COMET\DSK\;
006 = S ,\\COMETSERVER\COMET\SYS\;
007 = S ,\\COMETSERVER\COMET\OBJ\;
008 = S ,\\COMETSERVER\COMET\PAY\;
009 = S ,\\COMETSERVER\COMET\SRN\;
010 = S ,\\COMETSERVER\COMET\SRX\;
011 = S ,\\COMETSERVER\COMET\GAM\;
012 = S ,\\COMETSERVER\COMET\WRD\;
013 = S ,\\COMETSERVER\COMET\SEC\;
014 = S ,\\COMETSERVER\COMET\AAA\;
015 = S ,\\COMETSERVER\COMET\DSX\;
016 = S ,\\COMETSERVER\COMET\SPL\;
017 = S ,\\COMETSERVER\COMET\SL1\;
018 = S ,\\COMETSERVER\COMET\OLD\;
019 = S ,\\COMETSERVER\COMET\REP\;
020 = S ,\\COMETSERVER\COMET\SR\;
021 = S ,\\COMETSERVER\COMET\LE\;
022 = S ,\\COMETSERVER\COMET\LEP\;
023 = S ,\\COMETSERVER\COMET\UTR\;
024 = S ,\\COMETSERVER\COMET\XTL\;
025 = S ,\\COMETSERVER\COMET\TST\;
026 = S ,\\COMETSERVER\COMET\NEW\;
027 = S ,\\COMETSERVER\COMET\MNT\;
028 = S ,\\COMETSERVER\COMET\TMP\;
029 = S ,\\COMETSERVER\COMET\COS\;
030 = S ,\\COMETSERVER\COMET\J03\;
031 = S ,\\COMETSERVER\COMET\J04\;
032 = S ,\\COMETSERVER\COMET\J05\;
033 = S ,\\COMETSERVER\COMET\J06\;
034 = S ,\\COMETSERVER\COMET\J07\;
035 = S ,\\COMETSERVER\COMET\J08\;
036 = L ,C:\COMET\LOC\;
037 = S ,\\COMETSERVER\COMET\DLG\;
038 = S ,\\COMETSERVER\COMET\DMW\;
039 = S ,\\COMETSERVER\COMET\WDL\;
040 = S ,\\COMETSERVER\COMET\IBS\;
041 = C ,$(CATEMP);