I think that is a wonderful idea, Charles. I will be adding trending analysis to our next major release XLr8Resizer. It will be graphical using the built in report writer called BIRT that is a Eclipse plug-in.
Regards, Doug www.u2logic.com On Thu, Oct 6, 2011 at 7:29 AM, Charles Stevenson <stevenson.c...@gmail.com>wrote: > My experience is a couple years old. FAST is a solid tool. Shoes for the > cobbler's children. Automates IT. What a concept. > > But I added my own history component to FAST so I could see file trends > over time. > This trending history helped me take a system that was always crying for > more resizes beyond the scheduled quarterly maintenance of 6-8 hrs each, to > one that I could do maintenance yearly before the Christmas busy season, and > go home early. (ok, add in an occasional emergency.) > > Weekly, I would run FAST's statistical analysis (just analysis, not > resizes) on both dynamic & hashed), but that gave me only a snapshot. > I wanted to be alerted to files that suddenly deviated from their usual > growth pattern. > For example, some files behave differently different times of the business > cycle. I could see where I needed better data purges, what part of the ap > was being exercised in new ways because of changing business needs, etc.. > > When time for actual resizes, I would alter FAST's recommendations > according to my trending analysis, targeting where I expected each file to > be between resize opportunities. That helped me figure out which should be > static, which type-30, which needed minimum.modulus set, etc.. > > (Jeff, are you listening? Put this trending history stuff in the product. > I'm thinking this new DataVu offering might allow a good user interface for > this.) > > Weekly analysis effectively scans for broken files, too. > > I had a smallish window to do the weekly job, but, guided by history, I > could load balance the task across several phantoms run in parallel. That > was done programatically, not by the GUI. It's well documented in the FAST > manual. > > FAST also made my scheduled maintenance downtime easier because it allows > multiple instances to run, however many your iron can handle. You can > isolate huge files in their own process. > > Yes, you can do the same manually without FAST. But you (meaning "I") > usually end up with one-shot paragraphs -- that have spelling errors . . . > > I suppose I could have done most of that without FAST, but FAST made it > easier and I didn't have to reinvent the wheel. And Jeff & Peggy - who are > responsive & easy to work with - have already worked out the bugs. > > cds > > On 10/4/2011 10:41 AM, Eric Armstrong wrote: > >> Would anyone who is using FAST (File Analysis and Sizing Tool) care to >> comment about it? Experiences with it, plus and minuses? Does it deliver as >> advertised? >> > > ______________________________**_________________ > U2-Users mailing list > U2-Users@listserver.u2ug.org > http://listserver.u2ug.org/**mailman/listinfo/u2-users<http://listserver.u2ug.org/mailman/listinfo/u2-users> > _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users