Jerry,
As previous posts have pointed out a Dictionary is no different than any other
file. It need to be properly sized for the data it holds. When properly
sized will have maximum performance by definition. No need to 'split'
files....
At TCL: 'file.stat DICT filename'
Example: 'file.stat DICT PARTS'
If file.stat has a new file size recommendation on its last line then run
(after hours with no users or running processes that may use the dictionary):
At TCL: '!memresize DICT filename new.size'
Example: '!memresize DICT PARTS 1009'
Marc Rutherford
Principal Programmer Analyst
Advanced Bionics LLC
661) 362 1754
-----Original Message-----
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Jeffrey Butera
Sent: Wednesday, August 07, 2013 3:07 AM
To: U2 Users List
Cc: U2 Users List
Subject: Re: [U2] Large DICT affecting I/O
Thanks to those who replied.
1) we have tools to easily edit dictionaries of any size (one of the few
benefits of Datatel/ Ellucian)
2) we have tools to monitor and resize dictionaries just like any other file (
also a Datatel benefit)
It's more of a general question about performance. We import data from the
Common Application which has almost 2000 data attributes per person. Thus
having a large DICT isn't sloppy or lazy work on our end, it's a necessity of
the data.
Thus the question is better stated as:
Is unidata performance better if we stuff all 2000 elements in a single DICT or
break the data into multiple (eg: 4) files of 500 elements each?
When we work with this data we need all 2000 elements so is reading 4 or 5
separate tables any more efficient than reading a single large table of 2000
elements?
Jeffrey Butera, PhD
Associate Director for Application and Web Services Information Technology
Hampshire College
413-559-5556
On Aug 6, 2013, at 11:16 PM, Doug Averch <dave...@u2logic.com> wrote:
> Hi Jeffery:
>
> We have a client with 6,000 dictionaries items and they have no
> performance problems If the dictionary is sized correctly, there
> generally is no performance hit. However, editing it with some tools
> is a pain because it takes quite a long time to read them.
>
> Regards,
> Doug
> www.u2logic.com
> "XLr8Dictionary Editor for large dictionary editing"
>
> On Tue, Aug 6, 2013 at 9:08 PM, jeffrey Butera <jbut...@hampshire.edu>wrote:
>
>> 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<http://listser
>> ver.u2ug.org/mailman/listinfo/u2-users>
> _______________________________________________
> 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
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
