VSS DB import speed
-
Nishant Sivakumar wrote: Is this Normal? It's a P-4 2.8 with 1 GB RAM. Yes: it doesn't matter. VSS is not client/server so be prepared for: 1. Huge network traffic (probably that's why Outlook is also not responding). Since it's based on a file share, you can't compress it. 2. Corrupt databases. 3. Not scalable - the "server" needs to know a lot of things about the clients (e.g., who/where/when it has been checked out). 4. VSS is uncacheable The only reasonably reliable scenario for using VSS is a single developer, on a single machine, with small projects. I see dead pixels Yes, even I am blogging now!
I am importing from a local disk, so it's not a n/w traffic issue. I do hope the database is not corrupt :-( So, maybe I should wait a few more hours eh? One puzzling thing is that it's stopped adding files to the disk - as in the directories it created are not increasing in size anymore :-( But it's still taking all the CPU - so I have no idea what its trying to do. Its minimized now and the window is not restoring - so I half-fear it might have died a while ago and I am just watching its corpse take up all my CPU :((
-
I began importing (restoring) a VSS DB this morning (around 9 AM) - it was just under 500 MB - and now it's 2:17 PM and it's still not done. My entire machine is frozen up, CPU is at 100%, and the only two responsive programs are FF and IE. Nothing else (including Outlook) respond at all. Is this Normal? It's a P-4 2.8 with 1 GB RAM. Nish :~
w00t.JPG (10 Kb) Ngya ngya ngya ngya ngya Ngya ngya ngya ngya ngya Thanks all :-) Nish :-D
-
w00t.JPG (10 Kb) Ngya ngya ngya ngya ngya Ngya ngya ngya ngya ngya Thanks all :-) Nish :-D
Took 6 hours exactly :-)
-
OK - looks like VSS is stuck as its window is not restoring (it is minimized to the taskbar). If I force-kill it, when I restart, can I resume the restore?
Sometimes you would really wish the application will popup a message saying "I am hanged. Please kill me.", do you? :-> Weiye Chen Life is hard, yet we are made of flesh...
-
Sometimes you would really wish the application will popup a message saying "I am hanged. Please kill me.", do you? :-> Weiye Chen Life is hard, yet we are made of flesh...
Weiye Chen wrote: Sometimes you would really wish the application will popup a message saying "I am hanged. Please kill me.", do you? Not really, but I wish apps that are busy doing something would use threads properly. Hard to believe that a tool written by employees of the same company that wrote the OS does not use threads properly.
-
I am importing from a local disk, so it's not a n/w traffic issue. I do hope the database is not corrupt :-( So, maybe I should wait a few more hours eh? One puzzling thing is that it's stopped adding files to the disk - as in the directories it created are not increasing in size anymore :-( But it's still taking all the CPU - so I have no idea what its trying to do. Its minimized now and the window is not restoring - so I half-fear it might have died a while ago and I am just watching its corpse take up all my CPU :((
Nishant Sivakumar wrote: I do hope the database is not corrupt When I ran VSS (a few years ago, it was with VS 6.0, IIRC), I recall having to run Analyze.exe (or analyze6.exe, I don't remember exactly) every night to check our database for corruption. A couple of times a week, it found corruptions and we lost a few very old versions of our code. I don't know how it's called now, but I'd recommend you to run some DB analysis and recovery tool for VSS before writing more to it. Maybe VSS is hanging because of some corruption. I see dead pixels Yes, even I am blogging now!
-
Nishant Sivakumar wrote: I do hope the database is not corrupt When I ran VSS (a few years ago, it was with VS 6.0, IIRC), I recall having to run Analyze.exe (or analyze6.exe, I don't remember exactly) every night to check our database for corruption. A couple of times a week, it found corruptions and we lost a few very old versions of our code. I don't know how it's called now, but I'd recommend you to run some DB analysis and recovery tool for VSS before writing more to it. Maybe VSS is hanging because of some corruption. I see dead pixels Yes, even I am blogging now!
I think I'll run some tool and analyze the DB to see if its correct.
-
Took 6 hours exactly :-)
Nishant Sivakumar wrote: Took 6 hours Just Six Hour! :-D
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers, Alok Gupta
-
Weiye Chen wrote: Sometimes you would really wish the application will popup a message saying "I am hanged. Please kill me.", do you? Not really, but I wish apps that are busy doing something would use threads properly. Hard to believe that a tool written by employees of the same company that wrote the OS does not use threads properly.
Nishant Sivakumar wrote: Hard to believe that a tool written by employees of the same company that wrote the OS does not use threads properly. Was it conceived at Microsoft, or did they buy it and make it "visual?"
"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown
-
Nishant Sivakumar wrote: Hard to believe that a tool written by employees of the same company that wrote the OS does not use threads properly. Was it conceived at Microsoft, or did they buy it and make it "visual?"
"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown
MS bought the product known as SourceSafe sometime back in the late 90's. We used it before it was an MS product. MS developed a product initally called "Delta" that was to be their solution but it had too many usability problems to see the light of day. I went to a MS conference in Minneapolis back then and they were handing out glossy marketing brochures for Delta. When it had not been formally released within 6 months I asked our MS sales guy about it and he said that it was being dropped. (Yes, we actually had a MS sales guy come to our offices on a fairly irregular basis.) In any event, MS bought it and has not cleaned up the original SourceSafe usabilty issues. What do you expect from a company who's motto is: "We collect the money, you do the work."
-
MS bought the product known as SourceSafe sometime back in the late 90's. We used it before it was an MS product. MS developed a product initally called "Delta" that was to be their solution but it had too many usability problems to see the light of day. I went to a MS conference in Minneapolis back then and they were handing out glossy marketing brochures for Delta. When it had not been formally released within 6 months I asked our MS sales guy about it and he said that it was being dropped. (Yes, we actually had a MS sales guy come to our offices on a fairly irregular basis.) In any event, MS bought it and has not cleaned up the original SourceSafe usabilty issues. What do you expect from a company who's motto is: "We collect the money, you do the work."
I used both SourceSafe and Delta. My comment/question to Nish was more along the lines of "If Microsoft bought SourceSafe and did nothing to it other than make is 'visual', that would explain why it may not use threads properly."
"Ideas are a dime a dozen. People who put them into action are priceless." - Unknown
-
I began importing (restoring) a VSS DB this morning (around 9 AM) - it was just under 500 MB - and now it's 2:17 PM and it's still not done. My entire machine is frozen up, CPU is at 100%, and the only two responsive programs are FF and IE. Nothing else (including Outlook) respond at all. Is this Normal? It's a P-4 2.8 with 1 GB RAM. Nish :~
Yep, that is about right.... The strategy we employ is to export the VSS database into smaller sections. Importing the smaller sections may not take up less time (although it seems like it sometimes) but it releases VSS back to you sooner. Nishant Sivakumar wrote: I began importing (restoring) a VSS DB this morning (around 9 AM) - it was just under 500 MB - and now it's 2:17 PM and it's still not done. My entire machine is frozen up, CPU is at 100%, and the only two responsive programs are FF and IE. Nothing else (including Outlook) respond at all. Is this Normal? It's a P-4 2.8 with 1 GB RAM.
-
I began importing (restoring) a VSS DB this morning (around 9 AM) - it was just under 500 MB - and now it's 2:17 PM and it's still not done. My entire machine is frozen up, CPU is at 100%, and the only two responsive programs are FF and IE. Nothing else (including Outlook) respond at all. Is this Normal? It's a P-4 2.8 with 1 GB RAM. Nish :~
I'm not surprised. I maintain a VSS data base that's about 1Gb in size. I tried archiving it once; after it ran 13 hours over night, and still wasn't done, I went back to my original backup method. My original method:
XCOPYthe whole directory tree to a local drive and then ZIP it up into a single file. Even now, over a 100Mbit Ethernet, it only takes about an hour to back the thing up. This approach also lets me run the ANALYZE tool over the local copy, rather than having to lock down the 'live' data base. The only time I lock the live data base is if I actually have to run a repair, which is only 2-3 times per year.
Software Zen:
delete this;
