I would suggest that rather than the DICTIONARY being a performance problem, which can be easily overcome with a suitably sized file, the REAL impact may be in day to day processing where this file might be getting referenced to display a dozen or so fields, but each I/O is actually pulling in much, Much, MUCH more, pulling in 2 orders of magnitude more fields than it needs to
Sure, UD/UV/MV ALLOWS you to DO this sort of thing, but I would respectfully suggest that you shouldn't necessarily do so. If people adopt bad habits like this, they tend to just keep on evolving, and I suspect if performance is currently "OK" (thanks to ever faster hardware), there is probably no desire to go through the pain associated with "fixing" this (or budget :-) -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of jeffrey Butera Sent: Wednesday, August 7, 2013 1:09 PM To: U2 Users List Subject: [U2] Large DICT affecting I/O I'm curious how large of a DICTionary some of you have worked with and, in particular, how very large DICTs can adversely affect applications. We have a DICT approaching 1500 data elements (no idescs) - which is quite large for us. But I'm curious if others have DICTs this large or larger and have no adverse affect on their application performance. This is Unidata 7.3.4 if it matters. -- Jeffrey Butera, PhD Associate Director for Application and Web Services Information Technology Hampshire College 413-559-5556 _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org 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
