Bravo on great speed improvement in LR5!

I'm currently in the process of editing large sets of close to 300 photos each.  My workflow needs me to go through each single shot, calibrate them, and eventually make a selection of around 100 good photos per set.  I often navigate between the Library and Develop modules, and I use pretty much all tools (as necessary) when calibrating/editing the shots.  My files are D800 raw files. Note also that my library contains 13 years of photography work, with around 250,000 photos (of various sources evidently).
I just wanted to take a few minutes off my editing process to comment on the huge improvement on speed I am experiencing in LR5 over LR4.
In LR4, my workflow with my D800 files was very painful, with all the slugginess I would get everytime I moved from the Develop module to the Library Module, and everytime I used tools in the develop module.  There was lag virtually everywhere.  I'm on a very up to date system, with SSD drives both for the phtoos I work on, and my system disc. 
Since LR5, I can honestly say it feels pleasant once again to edit my photos.  As where I feared opening LR4 to do my job, I now look forward again to visit my shots. 
I read on the forum about the sharpness issue in lower res exports, and I'm sure there are a few more things to fix here and there.  But the HUGE improvement in responsiveness and speed in the application makes LR5 a real winner to me.  Speed is definitly a main issue that should always be addressed first with each update, always trying to improve on it and make the workflow as pleasant as possible so that we, as photographers, have to focus only on one thing: creativity. 
I'm glad this issue was addressed with LR5, and my only wish would have been to see it addressed sooner in LR4.
Back to editing I go...
cheers!

I'm currently in the process of editing large sets of close to 300 photos each.  My workflow needs me to go through each single shot, calibrate them, and eventually make a selection of around 100 good photos per set.  I often navigate between the Library and Develop modules, and I use pretty much all tools (as necessary) when calibrating/editing the shots.  My files are D800 raw files. Note also that my library contains 13 years of photography work, with around 250,000 photos (of various sources evidently).
I just wanted to take a few minutes off my editing process to comment on the huge improvement on speed I am experiencing in LR5 over LR4.
In LR4, my workflow with my D800 files was very painful, with all the slugginess I would get everytime I moved from the Develop module to the Library Module, and everytime I used tools in the develop module.  There was lag virtually everywhere.  I'm on a very up to date system, with SSD drives both for the phtoos I work on, and my system disc. 
Since LR5, I can honestly say it feels pleasant once again to edit my photos.  As where I feared opening LR4 to do my job, I now look forward again to visit my shots. 
I read on the forum about the sharpness issue in lower res exports, and I'm sure there are a few more things to fix here and there.  But the HUGE improvement in responsiveness and speed in the application makes LR5 a real winner to me.  Speed is definitly a main issue that should always be addressed first with each update, always trying to improve on it and make the workflow as pleasant as possible so that we, as photographers, have to focus only on one thing: creativity. 
I'm glad this issue was addressed with LR5, and my only wish would have been to see it addressed sooner in LR4.
Back to editing I go...
cheers!

Similar Messages

  • Massive Disk Speed Improvement Plan

    I am moving forward with a disk storage speed improvement plan using my Dell Precision T5400 workstation as the test bed.
    Specifically, my goal is to create a super fast 2 TB drive C: from four OCZ Vertex 3 480GB SATA3 SSD drives in RAID 0 configuration.  This will replace an already fast RAID 0 array made from two Western Digital 1TB RE4 drives.
    So far I have ordered two of these fast SSD drives, along with what is touted to be a very good value in high performance SATA3 RAID controllers, a Highpoint 2420SGL.  I'll get started with this combination and get to know it first as a data drive before trying to make it bootable.
    Getting any kind of hard information online about putting SSDs into RAID is a bit like pulling teeth, so I'm not 100% confident that these parts will work perfectly together, but I think the choice of SSD drives is the right one.  I had briefly considered a PCIe RevoDrive SSD card made by OCZ, but was just too esoteric...  I'm actually getting double the storage this way for the same price, I can swap to a different RAID controller if need be, and these drives can easily be ported to any new workstation I may get in the future.
    Notably, some early concerns with using SSD in RAID configurations (and things like TRIM commands) have already been alleviated, as the drives are now quite intelligent in their internal "garbage collection" processes.  I've verified this with the engineers at OCZ.  They have said that with these modern SSD drives you really don't have to worry about them being special - just use them as you would a normal drive.
    Once I get the first two SSDs set up in RAID 0 I'll specifically do some comparisons with saving large files and also using the array as the Photoshop scratch drive, vs. the spinning 1 TB drive I have in that role now.
    Assuming all goes well, I'll then add the additional two SSDs to complete the four drive array.  After a quick test of that, I'll see if I can restore a Windows System Image backup made from my 2 TB C: (spinning drive) array, which (if it works) will let me hit the ground running using the same exact Windows setup, just faster.
    My current C: drive, made from two Western Digital 1 TB RE4 drives, delivers about 210 MB/sec throughput with very large files, with 400 MB/sec bursts with small files (these drives have big caches).  Where they fall down dismally (by comparison to SSD) is operations involving seeking...  The PassMark advanced "Workstation" benchmark generates random small accesses such as what you might see during real work (and I can hear the drives seeking like crazy) results in a meager 4 MB/sec result.
    My current D: drive, a single Hitachi 1 TB spinning drive, clocks in at about 100 MB/sec for large reads/writes.
    The SSD array should push the throughput up at least 5x as compared to my current drive C: array, to over 1 GB/sec, but the biggest gain should be with random small accesses (no seek time in an SSD), where I'm hoping to see at leasdt a 25x improvement to over 100 MB/second.  That last part is what's going to speed things up from an every day usage perspective.
    I imagine that when the dust settles on this build-up, I'll end up pointing virtually everything at drive C:, including the Photoshop scratch file, since it will have such a massively fast access capability.  It will be interesting to experiment.  I suppose I'll have to come up with some gargantuan panoramas to stitch in order to force Photoshop to go heavily to the scratch drive for testing.
    I'll let you all know how it works out, and I'll be sure and do before/after comparisons of real use scenarios (big files in Photoshop, and various other things).  Perhaps fully my "real world" results can help others looking to get more Photoshop performance out of their systems understand what SSD can and can't do for them.
    I welcome your thoughts and experiences.
    -Noel

    Not sure who might be following this thread, but I have executed the final phase of this plan, restoring a system backup from my spinning drive array onto the new 4 drive SSD array.
    All went off without a hitch, I have my same system configuration including all apps and everything just as it was, except everything is now MUCH faster.
    The 4 drive array achieves a staggering 1.74 gigabytes/second sustained throughput rate.
    Windows 7 WEI score is 7.9 for the Primary hard disk category.
    Windows boots up quickly, everything starts immediately, nothing bogs the system down, and just overall everything feels very fluid and snappy.  And there is no seeking noise from the drives.
    Regarding what this has done for Photoshop...  I've only tested on Photoshop CS6 beta so far today, but everything is incrementally improved.  Startup time is faster, things seem more smooth and fluid while editing overall, and a benchmark I created using an action to run a lot of image adjustment operations on a big, multi-layer image ran this long to completion:
    When the file is opened from (and the Photoshop scratch file is on) a single spinning disk: 
    4 minutes 26 seconds (266 seconds)
    When the file is opened from (and the scratch file was is on) a fast array of spinning drives: 
    3 minutes 45 seconds (225 seconds)
    When the entire system is run from the SSD array: 
    2 minutes 31 seconds (151 seconds)
    During the action, because so many steps are performed on the big file, Photoshop writes a 30+ gigabyte scratch file on the scratch drive.
    Summary
    Clearly the very fast disk access markedly improves Photoshop's speed when it uses scratch space. 
    Plus copying big image files around is virtually instantaneous. 
    I don't use Bridge myself, but I have noticed that all the image thumbnails (via FastPictureViewer Codec Pack) just show up immediately in Explorer windows and Photoshop File Open/Save dialogs.  We can only assume this kind of drive speed would really make Bridge blaze through its operations as well.
    Following my footsteps would be expensive, but it can really work.
    -Noel

  • The Size of prddata increasing with great speed . dbf files are increasing

    Hi
    the Size of prddata increasing with great speed . dbf files are increasing which result in 100 % space utilization.
    can I delete temp01.dbf files.what is possible solution for this as dbf files are increasing with unexpected great speed.
    Thanks
    Rahul

    db version is 9.2.0.6.0
    Application 11.5.10.2
    Allert.log is showing error
    ORA-04098: trigger 'APPS.XXXX_APPS_LOGON_TRG' is invalid and failed re-validation
    output of query
    select object_name
    from dba_objects
    where object_type = 'TRIGGER'
    and status = 'INVALID';
    OBJECT_NAME
    AX_AP_CHECKS_ARU1
    AX_AP_CHECKS_ARU2
    AX_AP_CHECKS_BRI1
    AX_AP_HOLDS_ARI1
    AX_AP_HOLDS_ARU1
    AX_AP_HOLD_CODES_ARU1
    AX_AP_INVOICES_ARU1
    AX_AP_INVOICES_ARU2
    AX_AP_INVOICES_ARU3
    AX_AP_INVOICES_BRDI1
    AX_AP_INVOICE_DIST_ARDI1
    OBJECT_NAME
    AX_AP_INVOICE_DIST_ARDI2
    AX_AP_INVOICE_DIST_ARU1
    AX_AP_INVOICE_DIST_ARU2
    AX_AP_INVOICE_PAY_ARDI1
    AX_DOCUMENT_STATUSES_BRU1
    AX_DOCUMENT_STATUSES_BRU2
    BEN_EXT_ADD_EVT
    FF_GLOBALS_F_BRI
    GHR_PER_ADDRESSES_AFIUD
    HRI_EDW_CMPSTN_SNPSHT_DTS_WHO
    HRI_EDW_USER_PERSON_TYPES_WHO
    OBJECT_NAME
    HRI_GEN_HRCHY_SUMMARY_WHO
    HRI_INV_SPRTN_RSNS_WHO
    HRI_MB_WMV_WHO
    HRI_ORG_HRCHY_SUMMARY_WHO
    HRI_ORG_PARAMS_WHO
    HRI_ORG_PARAM_LIST_WHO
    HRI_PRIMARY_HRCHYS_WHO
    HRI_RECRUITMENT_STAGES_WHO
    HRI_SERVICE_BANDS_WHO
    HRI_SUPV_HRCHY_SUMMARY_WHO
    HR_ORG_INFO_BRI
    OBJECT_NAME
    HR_PAY_IF_ASG_COST_BRD
    HR_PAY_IF_ELE_ENT_ASD
    HR_PAY_IF_PERSON_ARU
    HR_PAY_IF_PPM_BRD
    HR_PAY_IF_PPM_NO_UPDATE2_ARU
    HR_PAY_IF_PPM_NO_UPDATE_ARU
    HR_PA_MAINTAIN_ORG_HIST_BRI
    HXC_ALIAS_DEFINITIONS_WHO
    HXC_ALIAS_TYPES_WHO
    HXC_ALIAS_TYPE_COMPONENTS_WHO
    HXC_ALIAS_VALUES_WHO
    OBJECT_NAME
    HXC_APPROVAL_COMPS_WHO
    HXC_APPROVAL_PERIOD_COMPS_WHO
    HXC_APPROVAL_PERIOD_SETS_WHO
    HXC_APPROVAL_STYLES_WHO
    HXC_BLD_BLK_INFO_TYPE_USAG_WHO
    HXC_DATA_APP_RULE_USAGES_WHO
    HXC_DEPOSIT_PROCESSES_WHO
    HXC_ENTITY_GROUPS_WHO
    HXC_ENTITY_GROUP_COMPS_WHO
    HXC_ERRORS_WHO
    HXC_LAYOUTS_WHO
    OBJECT_NAME
    HXC_LAYOUT_COMPONENTS_WHO
    HXC_LAYOUT_COMP_DEFINITION_WHO
    HXC_LAYOUT_COMP_PROMPTS_WHO
    HXC_LAYOUT_COMP_QUALIFIERS_WHO
    HXC_LAYOUT_COMP_QUAL_RULES_WHO
    HXC_MAPPINGS_WHO
    HXC_MAPPING_COMPONENTS_WHO
    HXC_MAPPING_COMP_USAGES_WHO
    HXC_PREF_DEFINITIONS_WHO
    HXC_PREF_HIERARCHIES_WHO
    HXC_RECURRING_PERIODS_WHO
    OBJECT_NAME
    HXC_RESOURCE_RULES_WHO
    HXC_RETRIEVAL_PROCESSES_WHO
    HXC_RETRIEVAL_RANGES_WHO
    HXC_RETRIEVAL_RULES_WHO
    HXC_RETRIEVAL_RULE_COMPS_WHO
    HXC_TIME_BUILDING_BLOCKS_WHO
    HXC_TIME_CATEGORIES_WHO
    HXC_TIME_CATEGORY_COMPS_WHO
    HXC_TIME_ENTRY_RULES_WHO
    HXC_TIME_RECIPIENTS_WHO
    HXC_TIME_SOURCES_WHO
    OBJECT_NAME
    HXC_TK_GROUPS_WHO
    HXC_TK_GROUP_QUERIES_WHO
    HXC_TK_GROUP_QUERY_CRITERI_WHO
    HXC_TRANSACTIONS_WHO
    HXC_TRANSACTION_DETAILS_WHO
    HXT_ADD_ASSIGN_INFO_F_WHO
    HXT_ADD_ELEM_INFO_F_WHO
    HXT_DET_HOURS_WORKED_F_WHO
    HXT_EARNING_POLICIES_WHO
    HXT_EARNING_RULES_WHO
    HXT_EARN_GROUPS_WHO
    OBJECT_NAME
    HXT_EARN_GROUP_TYPES_WHO
    HXT_ERRORS_F_WHO
    HXT_HOLIDAY_CALENDARS_WHO
    HXT_HOLIDAY_DAYS_WHO
    HXT_HOUR_DEDUCTION_RULES_WHO
    HXT_HOUR_DEDUCT_POLICIES_WHO
    HXT_PREM_ELIGBLTY_POLICIES_WHO
    HXT_PREM_ELIGBLTY_POL_RULE_WHO
    HXT_PREM_ELIGBLTY_RULES_WHO
    HXT_PREM_INTERACT_POLICIES_WHO
    HXT_PREM_INTERACT_RULES_WHO
    OBJECT_NAME
    HXT_PROJECTS_WHO
    HXT_ROTATION_PLANS_WHO
    HXT_ROTATION_SCHEDULES_WHO
    HXT_SHIFTS_WHO
    HXT_SHIFT_DIFF_POLICIES_WHO
    HXT_SHIFT_DIFF_RULES_WHO
    HXT_SUM_HOURS_WORKED_F_WHO
    HXT_TASKS_WHO
    HXT_TIMECARDS_F_WHO
    HXT_VARIANCES_WHO
    HXT_WEEKLY_WORK_SCHEDULES_WHO
    OBJECT_NAME
    HXT_WORK_SHIFTS_WHO
    OTA_ACTIVITY_DEFINITIONS_WHO
    OTA_BOOKING_DEALS_WHO
    OTA_BOOKING_STATUS_HISTORI_WHO
    OTA_CATEGORY_USAGES_WHO
    OTA_COMPETENCE_LANGUAGES_WHO
    OTA_CROSS_CHARGES_WHO
    OTA_DELEGATE_BOOKINGS_WHO
    OTA_EVENT_ASSOCIATIONS_WHO
    OTA_FINANCE_HEADERS_WHO
    OTA_FINANCE_LINES_WHO
    OBJECT_NAME
    OTA_HR_GL_FLEX_MAPS_WHO
    OTA_ILN_XML_PROCESSES_WHO
    OTA_NOTRNG_HISTORIES_WHO
    OTA_PRICE_LISTS_WHO
    OTA_PRICE_LIST_ENTRIES_WHO
    OTA_RESOURCE_ALLOCATIONS_WHO
    OTA_RESOURCE_DEFINITIONS_WHO
    OTA_RESOURCE_USAGES_WHO
    OTA_SKILL_PROVISIONS_WHO
    OTA_SUPPLIABLE_RESOURCES_WHO
    OTA_TRAINING_PLANS_WHO
    OBJECT_NAME
    OTA_TRAINING_PLAN_COSTS_WHO
    OTA_TRAINING_PLAN_MEMBERS_WHO
    OTA_VENDOR_SUPPLIES_WHO
    PAY_ASSIGNMENT_ACTIONS_BRD
    PAY_ASSIGNMENT_ACTIONS_BRU
    PAY_BALANCE_BATCH_LINES_BRIUD
    PAY_BALANCE_FEEDS_ARD
    PAY_BALANCE_FEEDS_ARI
    PAY_BALANCE_FEEDS_ARU
    PAY_DEFINED_BALANCES_ARI
    PAY_DEFINED_BALANCES_BRD
    OBJECT_NAME
    PAY_ELEMENT_LINKS_T1
    PAY_ELEMENT_TYPES_T1
    PAY_ORG_PAYMENT_METHODS_F_OVN
    PAY_PAYMIX_LINE_INSERT
    PAY_PAYROLL_ACTIONS_BRD
    PAY_PAYROLL_ACTIONS_BRU
    PAY_PERSONAL_PAYMENT_METHO_OVN
    PAY_PERSONAL_PAY_METHODS_BRUI
    PAY_RUN_RESULTS_BRD
    PAY_TRIGGER_EVENTS_ARD
    PAY_ZA_TEMP_BRANCH_DETAILS_ARD
    OBJECT_NAME
    PAY_ZA_TEMP_BRANCH_DETAILS_ARI
    PAY_ZA_TEMP_BRANCH_DETAILS_ASI
    PA_MAINTAIN_ORG_HIST_BRD
    PER_ABV_OVN
    PER_ALL_ASSIGNMENTS_F_OVN
    PER_ALL_PEOPLE_F_ARIU
    PER_ALL_PEOPLE_F_OVN
    PER_ESTABLISHMENT_ATTN_CHLG
    PER_JOB_REQUIREMENTS_OVN
    PER_ORG_STRUCTURE_ELEMENTS_OVN
    PER_ORS_OVN
    OBJECT_NAME
    PER_OSV_OVN
    PER_PAY_PROPOSALS_CHLG
    PER_PAY_PROPOSALS_OVN
    PER_PERIODS_OF_SERVICE_OVN
    PER_POS_STRUCTURE_ELEMENTS_OVN
    PER_PROPOSAL_COMPS_OVN
    PER_QUERY_CRITERIA_OVN
    PER_RECRUITMENT_ACTIVITIES_OVN
    PER_REC_ACTIVITY_FOR_OVN
    PER_REQUISITIONS_OVN
    PER_VALID_GRADES_OVN
    OBJECT_NAME
    SET_HXT_BATCH_STATES_INS
    SSP_DEL_ORPHANED_ROWS
    SSP_MEDICALS_WHO
    SSP_STOPPAGES_WHO
    SSP_WITHHOLDING_REASONS_WHO
    BEN_ABR_EXTRA_INFO_WHO
    BEN_ABR_INFO_TYPES_WHO
    BEN_ACRS_PTIP_CVG_F_WHO
    BEN_BENEFICIARIES_F_WHO
    BEN_ACTL_PREM_VRBL_RT_RL_F_WHO
    BEN_ACTN_TYP_WHO
    OBJECT_NAME
    BEN_COVERED_DEPENDENTS_F_WHO
    BEN_VALID_DEPENDENT_TYPES_WHO
    BEN_ACTY_BASE_RT_CTFN_F_WHO
    BEN_ACTY_BASE_RT_F_WHO
    BEN_ACTY_RT_PYMT_SCHED_F_WHO
    BEN_ACTY_VRBL_RT_F_WHO
    BEN_AGE_FCTR_WHO
    BEN_AGE_RT_F_WHO
    BEN_APLCN_TO_BNFT_POOL_F_WHO
    OTA_ANNOUNCEMENTS_WHO
    BEN_APLD_DPNT_CVG_ELIG_PRF_WHO
    OBJECT_NAME
    BEN_BATCH_BNFT_CERT_INFO_WHO
    BEN_BATCH_COMMU_INFO_WHO
    BEN_BATCH_LER_INFO_WHO
    BEN_BATCH_PARAMETER_WHO
    HXT_TIMECLOCK_ERRORS_WHO
    BEN_BNFT_POOL_RLOVR_RQMT_F_WHO
    BEN_BNFT_PRVDR_POOL_F_WHO
    BEN_BNFT_VRBL_RT_F_WHO
    BEN_BNFT_VRBL_RT_RL_F_WHO
    FF_FORMULAS_F_WHO
    FF_ROUTE_PARAMETER_VALUES_WHO
    OBJECT_NAME
    BEN_CMBN_PLIP_F_WHO
    HXC_LOCKING_RULES_WHO
    GHR_COMPLAINTS2_WHO
    BEN_CM_TYP_F_WHO
    GHR_COMPL_AGENCY_APPEALS_WHO
    GHR_COMPL_CA_DETAILS_WHO
    GHR_COMPL_CA_HEADERS_WHO
    GHR_CPDF_TEMP_WHO
    GHR_DUAL_ACTIONS_WHO
    GHR_DUAL_PROC_METHODS_WHO
    HXC_SEEDDATA_BY_LEVEL_WHO
    OBJECT_NAME
    GHR_DUTY_STATIONS_F_WHO
    GHR_GROUPBOX_USERS_WHO
    BEN_CM_TYP_USG_F_WHO
    BEN_DED_SCHED_PY_FREQ_WHO
    BEN_DPNT_CVG_RQD_RLSHP_F_WHO
    GHR_POIS_WHO
    GHR_POSITION_DESCRIPTIONS_WHO
    BEN_DPNT_CVRD_ANTHR_PL_CVG_WHO
    GHR_PREMIUM_PAY_INDICATORS_WHO
    GHR_PROCESS_LOG_WHO
    OTA_IMPORT_HISTORIES_WHO
    OBJECT_NAME
    GHR_RESTRICTED_PROC_METHOD_WHO
    OTA_LEARNING_PATHS_WHO
    GHR_RIF_REGISTERS_WHO
    BEN_DPNT_OTHR_PTIP_RT_F_WHO
    GHR_ROUTING_GROUPS_WHO
    GHR_ROUTING_LISTS_WHO
    GHR_ROUTING_LIST_MEMBERS_WHO
    BEN_DSBLD_RT_F_WHO
    BEN_DSGNTR_ENRLD_CVG_F_WHO
    BEN_DSGN_RQMT_RLSHP_TYP_WHO
    BEN_EE_STAT_RT_F_WHO
    OBJECT_NAME
    BEN_ELCTBL_CHC_CTFN_WHO
    BEN_ELIGY_PRFL_RL_F_WHO
    BEN_ELIG_AGE_CVG_F_WHO
    BEN_ELIG_COMPTNCY_PRTE_F_WHO
    BEN_ELIG_NO_OTHR_CVG_PRTE_WHO
    HR_CANVAS_PROPERTIES_WHO
    BEN_ELIG_PRTT_ANTHR_PL_PRT_WHO
    HR_COMMENTS_WHO
    HR_DE_LIABILITY_PREMIUMS_F_WHO
    BEN_ELIG_PSTN_PRTE_F_WHO
    BEN_ELIG_PYRL_PRTE_F_WHO
    OBJECT_NAME
    BEN_ELIG_QUAL_TITL_PRTE_F_WHO
    HR_DM_APPLICATION_GROUPS_WHO
    BEN_ELIG_SCHEDD_HRS_PRTE_F_WHO
    HR_DM_DATABASES_WHO
    BEN_ELIG_SP_CLNG_PRG_PRTE_WHO
    HR_DM_DT_DELETES_WHO
    BEN_ELIG_STDNT_STAT_CVG_F_WHO
    HR_DM_EXP_IMPS_WHO
    BEN_ELIG_SUPPL_ROLE_PRTE_F_WHO
    HR_DM_GROUPS_WHO
    BEN_ELIG_SVC_AREA_PRTE_F_WHO
    OBJECT_NAME
    BEN_ELIG_TBCO_USE_PRTE_F_WHO
    HR_DM_HIERARCHIES_WHO
    HR_DM_LOADER_PARAMS_WHO
    BEN_ELIG_TO_PRTE_RSN_F_WHO
    BEN_ELIG_TTL_CVG_VOL_PRTE_WHO
    HR_DM_LOADER_PHASE_ITEMS_WHO
    BEN_ELIG_TTL_PRTT_PRTE_F_WHO
    HR_DM_MIGRATIONS_WHO
    HR_DM_MIGRATION_RANGES_WHO
    HR_DM_MIGRATION_REQUESTS_WHO
    HR_DM_PHASE_ITEMS_WHO
    OBJECT_NAME
    BEN_ENRLD_ANTHR_OIPL_RT_F_WHO
    BEN_ENRLD_ANTHR_PLIP_RT_F_WHO
    HR_DM_SEQUENCE_DEFINITIONS_WHO
    HR_DM_SEQUENCE_RANGES_WHO
    BEN_ENRT_BNFT_WHO
    OTA_TEST_QUESTIONS_WHO
    BEN_ENRT_PREM_WHO
    BEN_ENRT_PREM_RBV_WHO
    HR_EFC_ACTIONS_WHO
    OTA_UTEST_QUESTIONS_WHO
    OTA_UTEST_RESPONSES_WHO
    OBJECT_NAME
    BEN_ENRT_RT_WHO
    HR_EFC_ROUNDING_ERRORS_WHO
    BEN_ENRT_RT_RBV_WHO
    HR_EFC_WORKER_AUDITS_WHO
    BEN_EXTRA_INPUT_VALUES_WHO
    HR_EXCEPTION_USAGES_WHO
    BEN_EXT_CHG_EVT_LOG_WHO
    HR_FORM_CANVASES_B_WHO
    BEN_EXT_CRIT_CMBN_WHO
    BEN_EXT_CRIT_PRFL_WHO
    BEN_EXT_CRIT_TYP_WHO
    OBJECT_NAME
    BEN_EXT_CRIT_VAL_WHO
    BEN_EXT_DATA_ELMT_WHO
    BEN_EXT_DATA_ELMT_DECD_WHO
    BEN_EXT_DATA_ELMT_IN_RCD_WHO
    BEN_EXT_DFN_WHO
    BEN_EXT_FILE_WHO
    BEN_EXT_FLD_WHO
    HR_FORM_DATA_GROUPS_B_WHO
    BEN_EXT_INCL_CHG_WHO
    BEN_EXT_INCL_DATA_ELMT_WHO
    BEN_EXT_RCD_WHO
    OBJECT_NAME
    BEN_EXT_RCD_IN_FILE_WHO
    BEN_EXT_RSLT_WHO
    BEN_EXT_RSLT_DTL_WHO
    BEN_EXT_RSLT_ERR_WHO
    BEN_EXT_WHERE_CLAUSE_WHO
    BEN_FL_TM_PT_TM_RT_F_WHO
    BEN_GD_OR_SVC_TYP_WHO
    BEN_GNDR_RT_F_WHO
    BEN_GRADE_RT_F_WHO
    HR_FORM_DATA_GROUP_ITEMS_WHO
    BEN_HRLY_SLRD_RT_F_WHO
    OBJECT_NAME
    HR_FORM_ITEMS_B_WHO
    BEN_HRS_WKD_IN_PERD_FCTR_WHO
    BEN_HRS_WKD_IN_PERD_RT_F_WHO
    BEN_JOB_RT_F_WHO
    BEN_LBR_MMBR_RT_F_WHO
    BEN_LEE_RSN_F_WHO
    BEN_LEE_RSN_RL_F_WHO
    BEN_LER_BNFT_RSTRN_CTFN_F_WHO
    BEN_LER_BNFT_RSTRN_F_WHO
    BEN_LER_CHG_DPNT_CVG_CTFN_WHO
    BEN_LER_CHG_DPNT_CVG_F_WHO
    OBJECT_NAME
    BEN_LER_CHG_OIPL_ENRT_F_WHO
    BEN_LER_CHG_OIPL_ENRT_RL_F_WHO
    BEN_LER_CHG_PGM_ENRT_F_WHO
    BEN_LER_CHG_PLIP_ENRT_F_WHO
    BEN_LER_CHG_PLIP_ENRT_RL_F_WHO
    BEN_LER_CHG_PL_NIP_ENRT_F_WHO
    BEN_LER_CHG_PL_NIP_RL_F_WHO
    BEN_LER_CHG_PTIP_ENRT_F_WHO
    BEN_LER_ENRT_CTFN_F_WHO
    BEN_LER_EXTRA_INFO_WHO
    BEN_LER_F_WHO
    OBJECT_NAME
    HR_FORM_PROPERTIES_WHO
    HR_FORM_TAB_PAGES_B_WHO
    BEN_LER_INFO_TYPES_WHO
    BEN_LER_PER_INFO_CS_LER_F_WHO
    BEN_LER_RLTD_PER_CS_LER_F_WHO
    BEN_LER_RQRS_ENRT_CTFN_F_WHO
    BEN_LE_CLSN_N_RSTR_WHO
    BEN_LGL_ENTY_RT_F_WHO
    HR_FORM_TAB_STACKED_CANVAS_WHO
    BEN_LOS_RT_F_WHO
    HR_FORM_TEMPLATES_B_WHO
    OBJECT_NAME
    BEN_NO_OTHR_CVG_RT_F_WHO
    BEN_OIPLIP_F_WHO
    BEN_OPT_INFO_TYPES_WHO
    BEN_ORG_UNIT_PRDCT_F_WHO
    BEN_PAIRD_RT_F_WHO
    BEN_PCT_FL_TM_FCTR_WHO
    BEN_PCT_FL_TM_RT_F_WHO
    BEN_PER_CM_F_WHO
    BEN_PER_CM_F_RBV_WHO
    BEN_PL_GD_R_SVC_CTFN_F_WHO
    BEN_PL_PCP_WHO
    OBJECT_NAME
    BEN_PL_R_OIPL_PREM_BY_MO_F_WHO
    BEN_PL_TYP_F_WHO
    BEN_POPL_ENRT_TYP_CYCL_F_WHO
    BEN_POPL_ORG_F_WHO
    BEN_PPL_GRP_RT_F_WHO
    HR_KI_CONTEXTS_WHO
    BEN_PRTN_ELIG_PRFL_F_WHO
    HR_KI_HIERARCHIES_WHO
    BEN_PRTT_ANTHR_PL_RT_F_WHO
    BEN_PRTT_ASSOCD_INSTN_F_WHO
    BEN_PRTT_CLM_GD_OR_SVC_TYP_WHO
    OBJECT_NAME
    BEN_PRTT_ENRT_ACTN_F_WHO
    BEN_PRTT_ENRT_CTFN_PRVDD_F_WHO
    BEN_PRTT_ENRT_RSLT_F_RBV_WHO
    BEN_PRTT_PREM_BY_MO_F_WHO
    BEN_PRTT_PREM_F_WHO
    BEN_PRTT_REIMBMT_RECON_WHO
    BEN_PRTT_REIMBMT_RQST_F_WHO
    BEN_PRTT_RMT_APRVD_FR_PYMT_WHO
    BEN_PRTT_RMT_RQST_CTFN_PRV_WHO
    BEN_PRTT_RT_VAL_CTFN_PRVDD_WHO
    BEN_PRTT_RT_VAL_RBV_WHO
    OBJECT_NAME
    BEN_PSTL_ZIP_RT_F_WHO
    BEN_PSTN_RT_F_WHO
    BEN_PTD_BAL_TYP_F_WHO
    BEN_PTD_LMT_F_WHO
    BEN_PTIP_DPNT_CVG_CTFN_F_WHO
    HR_KI_HIERARCHY_NODE_MAPS_WHO
    HR_KI_INTEGRATIONS_WHO
    BEN_PTIP_F_WHO
    BEN_PTNL_LER_FOR_PER_WHO
    BEN_PTNL_LER_FOR_PER_RBV_WHO
    BEN_PYMT_CHECK_DET_WHO
    OBJECT_NAME
    BEN_PYMT_SCHED_PY_FREQ_WHO
    BEN_PYRL_RT_F_WHO
    BEN_PY_BSS_RT_F_WHO
    BEN_QUAL_TITL_RT_F_WHO
    BEN_QUA_IN_GR_RT_F_WHO
    BEN_REGN_F_WHO
    BEN_REGN_FOR_REGY_BODY_F_WHO
    HR_KI_OPTIONS_WHO
    BEN_REPORTING_WHO
    BEN_RLTD_PER_CHG_CS_LER_F_WHO
    BEN_ROLL_REIMB_RQST_WHO
    OBJECT_NAME
    BEN_RPTG_GRP_WHO
    HR_KI_SESSIONS_WHO
    HR_KI_TOPICS_WHO
    BEN_SCHEDD_ENRT_RL_F_WHO
    BEN_SCHEDD_HRS_RT_F_WHO
    HR_LEGISLATION_INSTALLATIO_WHO
    HR_LEGISLATION_SUB_INST_WHO
    BEN_STARTUP_CM_TYP_WHO
    HR_LOCATION_INFO_TYPES_WHO
    BEN_STARTUP_LERS_WHO
    BEN_STARTUP_REGN_WHO
    OBJECT_NAME
    BEN_SVC_AREA_F_WHO
    BEN_TTL_CVG_VOL_RT_F_WHO
    BEN_TTL_PRTT_RT_F_WHO
    BEN_VRBL_RT_PRFL_RL_F_WHO
    BEN_WTHN_YR_PERD_WHO
    HR_PATTERN_EXCEPTIONS_WHO
    BEN_WV_PRTN_RSN_CTFN_PL_F_WHO
    HR_PATTERN_PURPOSES_WHO
    HR_PATTERN_PURPOSE_USAGES_WHO
    BEN_WV_PRTN_RSN_PL_F_WHO
    BEN_WV_PRTN_RSN_PTIP_F_WHO
    OBJECT_NAME
    HR_PUMP_BATCH_HEADERS_WHO
    BEN_YR_PERD_WHO
    HR_PUMP_BATCH_LINE_USER_KE_WHO
    HR_PUMP_DEFAULT_EXCEPTIONS_WHO
    HR_PUMP_MAPPING_PACKAGES_WHO
    HR_PUMP_MODULE_PARAMETERS_WHO
    HR_QUEST_ANSWERS_WHO
    HR_QUEST_ANSWER_VALUES_WHO
    HR_QUEST_FIELDS_WHO
    HR_REPORT_LOOKUPS_WHO
    HR_SOFT_CODING_KEYFLEX_WHO
    OBJECT_NAME
    HR_SOURCE_FORM_TEMPLATES_WHO
    HR_SUMMARY_WHO
    HR_TAB_PAGE_PROPERTIES_B_WHO
    HR_TEMPLATE_CANVASES_B_WHO
    HR_TEMPLATE_DATA_GROUPS_WHO
    HR_TEMPLATE_ITEMS_B_WHO
    HR_TEMPLATE_ITEM_CONTEXTS_WHO
    HR_TEMPLATE_ITEM_CONTEXT_P_WHO
    HR_TEMPLATE_ITEM_TAB_PAGES_WHO
    HR_TEMPLATE_TAB_PAGES_B_WHO
    HR_TEMPLATE_WINDOWS_B_WHO
    OBJECT_NAME
    HR_WINDOW_PROPERTIES_B_WHO
    HR_WIP_LOCKS_WHO
    HR_WIP_TRANSACTIONS_WHO
    IRC_ALL_RECRUITING_SITES_WHO
    IRC_ASSIGNMENT_STATUSES_WHO
    IRC_DEFAULT_POSTINGS_WHO
    IRC_DOCUMENTS_WHO
    IRC_NOTIFICATION_PREFERENC_WHO
    IRC_POSTING_CONTENTS_WHO
    IRC_REC_TEAM_MEMBERS_WHO
    IRC_REFERENCES_WHO
    OBJECT_NAME
    IRC_VACANCY_CONSIDERATIONS_WHO
    IRC_VAC_ALLOWED_STATUS_TYP_WHO
    IRC_VARIABLE_COMP_ELEMENTS_WHO
    PAY_ACCRUAL_BANDS_WHO
    PAY_ACTION_INFORMATION_WHO
    PAY_ALL_PAYROLLS_F_WHO
    PAY_AU_MODULES_WHO
    PAY_AU_MODULE_PARAMETERS_WHO
    PAY_AU_PROCESS_MODULES_WHO
    PAY_BALANCE_CATEGORIES_F_WHO
    PAY_BALANCE_CLASSIFICATION_WHO
    OBJECT_NAME
    PAY_BALANCE_FEEDS_F_WHO
    PAY_BALANCE_TYPES_WHO
    PAY_BAL_ATTRIBUTE_DEFINITI_WHO
    PAY_CALENDARS_WHO
    PAY_CA_EMP_FED_TAX_INFO_F_WHO
    PAY_COST_ALLOCATION_KEYFLE_WHO
    PAY_DATETRACKED_EVENTS_WHO
    PAY_DEFINED_BALANCES_WHO
    PAY_DIMENSION_ROUTES_WHO
    PAY_ELEMENT_CLASSIFICATION_WHO
    PAY_ELEMENT_SETS_WHO
    OBJECT_NAME
    PAY_ELEMENT_SPAN_USAGES_WHO
    PAY_ELEMENT_TEMPLATES_WHO
    PAY_ELEMENT_TYPE_EXTRA_INF_WHO
    PAY_ELEMENT_TYPE_INFO_TYPE_WHO
    PAY_ELEMENT_TYPE_USAGES_F_WHO
    PAY_ELE_CLASSIFICATION_RUL_WHO
    PAY_EVENT_QUALIFIERS_F_WHO
    PAY_EVENT_UPDATES_WHO
    PAY_EVENT_VALUE_CHANGES_F_WHO
    PAY_EXTERNAL_ACCOUNTS_WHO
    PAY_FORMULA_RESULT_RULES_F_WHO
    OBJECT_NAME
    PAY_FREQ_RULE_PERIODS_WHO
    PAY_FUNCTIONAL_USAGES_WHO
    PAY_GROSSUP_BAL_EXCLUSIONS_WHO
    PAY_IE_PAYE_DETAILS_F_WHO
    PAY_INPUT_VALUES_F_WHO
    PAY_ITERATIVE_RULES_F_WHO
    PAY_JP_BANKS_WHO
    PAY_LEG_SETUP_DEFAULTS_WHO
    PAY_SHADOW_BALANCE_FEEDS_WHO
    PAY_SHADOW_BALANCE_TYPES_WHO
    PAY_TRIGGER_COMPONENTS_WHO
    OBJECT_NAME
    PAY_TRIGGER_EVENTS_WHO
    PAY_USER_ROWS_F_WHO
    PAY_US_CONTRIBUTION_HISTOR_WHO
    PAY_US_GARN_FEE_RULES_F_WHO
    PAY_US_GARN_LIMIT_RULES_F_WHO
    PAY_ZA_CDV_PARAMETERS_WHO
    PER_ABSENCE_ATTENDANCES_WHO
    PER_ABSENCE_ATTENDANCE_TYP_WHO
    PER_ABS_ATTENDANCE_REASONS_WHO
    PER_ASSESSMENT_TYPES_WHO
    PER_ASSIGNMENT_BUDGET_VALU_WHO
    OBJECT_NAME
    PER_ASSIGN_PROPOSAL_ANSWER_WHO
    PER_BF_BALANCE_AMOUNTS_WHO
    PER_BF_BALANCE_TYPES_WHO
    PER_BF_PAYROLL_RUNS_WHO
    PER_BF_PROCESSED_ASSIGNMEN_WHO
    PER_BOOKINGS_WHO
    PER_BUDGETS_WHO
    PER_BUDGET_ELEMENTS_WHO
    PER_BUDGET_VALUES_WHO
    PER_BUDGET_VERSIONS_WHO
    PER_CAGR_APIS_WHO
    OBJECT_NAME
    PER_CAGR_API_PARAMETERS_WHO
    PER_CAGR_ENTITLEMENTS_WHO
    PER_CAGR_ENTITLEMENT_ITEMS_WHO
    PER_CAGR_ENTITLEMENT_LINES_WHO
    PER_CAGR_ENTITLEMENT_RESUL_WHO
    PER_CAGR_GRADES_WHO
    PER_CAGR_GRADES_DEF_WHO
    PER_CAGR_GRADE_STRUCTURES_WHO
    PER_CAGR_LOG_WHO
    PER_CAGR_RETAINED_RIGHTS_WHO
    PER_CALENDAR_ENTRIES_WHO
    OBJECT_NAME
    PER_CAL_ENTRY_VALUES_WHO
    PER_CAREER_PATHS_WHO
    PER_CAREER_PATH_ELEMENTS_WHO
    PER_CHECKLIST_ITEMS_WHO
    PER_COBRA_COVERAGE_BENEFIT_WHO
    PER_COBRA_COVERAGE_PERIODS_WHO
    PER_COBRA_COVERAGE_STATUSE_WHO
    PER_COBRA_COV_ENROLLMENTS_WHO
    PER_COBRA_DEPENDENTS_F_WHO
    PER_COBRA_QFYING_EVENTS_F_WHO
    PER_COLLECTIVE_AGREEMENTS_WHO
    OBJECT_NAME
    PER_COMPETENCES_WHO
    PER_COMPETENCE_DEFINITIONS_WHO
    PER_COMPETENCE_ELEMENTS_WHO
    PER_CONTACT_EXTRA_INFO_F_WHO
    PER_CONTACT_INFO_TYPES_WHO
    PER_CONTRACTS_F_WHO
    PER_DEPLOYMENT_FACTORS_WHO
    PER_DISABILITIES_F_WHO
    PER_ELECTIONS_WHO
    PER_ELECTION_CANDIDATES_WHO
    PER_ELECTION_CONSTITUENCYS_WHO
    OBJECT_NAME
    PER_EMPDIR_ASSIGNMENTS_WHO
    PER_EMPDIR_IMAGES_WHO
    PER_EMPDIR_PEOPLE_WHO
    PER_EMPDIR_PHONES_WHO
    PER_ESTABLISHMENTS_WHO
    PER_ESTABLISHMENT_ATTENDAN_WHO
    PER_GEN_HIERARCHY_WHO
    PER_GEN_HIERARCHY_NODES_WHO
    PER_GEN_HIERARCHY_VERSIONS_WHO
    PER_GEN_HIER_NODE_TYPES_WHO
    PER_GRADES_WHO
    OBJECT_NAME
    PER_GRADE_DEFINITIONS_WHO
    PER_GRADE_SPINES_F_WHO
    PER_HTML_TOOLKIT_REC_TYPES_WHO
    PER_JOB_EVALUATIONS_WHO
    PER_JOB_EXTRA_INFO_WHO
    PER_JOB_GROUPS_WHO
    PER_JOB_INFO_TYPES_WHO
    PER_JOB_REQUIREMENTS_WHO
    PER_JP_ADDRESS_LOOKUPS_WHO
    PER_JP_BANK_LOOKUPS_ALL_WHO
    PER_JP_POSTAL_CODES_WHO
    OBJECT_NAME
    PER_KR_GRADES_WHO
    PER_KR_GRADE_AMOUNT_F_WHO
    PER_KR_G_POINTS_WHO
    PER_KR_G_POINT_AMOUNT_F_WHO
    PER_MEDICAL_ASSESSMENTS_WHO
    PER_MM_VALID_GRADES_WHO
    PER_NL_ABSENCE_ACTIONS_WHO
    PER_OBJECTIVES_WHO
    PER_ORGANIZATION_STRUCTURE_WHO
    PER_ORG_HRCHY_SUMMARY_WHO
    PER_ORG_STRUCTURE_ELEMENTS_WHO
    OBJECT_NAME
    PER_PARENT_SPINES_WHO
    PER_PARTICIPANTS_WHO
    PER_PAY_BASES_WHO
    PER_PAY_PROPOSAL_COMPONENT_WHO
    PER_PEOPLE_INFO_TYPES_WHO
    PER_PERFORMANCE_RATINGS_WHO
    PER_PERFORMANCE_REVIEWS_WHO
    PER_PERIODS_OF_PLACEMENT_WHO
    PER_PERSON_DLVRY_METHODS_WHO
    PER_PERSON_TYPE_USAGES_F_WHO
    PER_POSITION_DEFINITIONS_WHO
    OBJECT_NAME
    PER_POSITION_EXTRA_INFO_WHO
    PER_POSITION_INFO_TYPES_WHO
    PER_POS_STRUCTURE_ELEMENTS_WHO
    PER_POS_STRUCTURE_VERSIONS_WHO
    PER_PREVIOUS_EMPLOYERS_WHO
    PER_PREVIOUS_JOBS_WHO
    PER_PREVIOUS_JOB_USAGES_WHO
    PER_PREV_JOB_EXTRA_INFO_WHO
    PER_PREV_JOB_INFO_TYPES_WHO
    PER_PROPOSAL_CATEGORY_MEMB_WHO
    PER_PROPOSAL_CATEGORY_TYPE_WHO
    OBJECT_NAME
    PER_PROPOSAL_OFFER_PARAGRA_WHO
    PER_PROPOSAL_QUESTIONS_ADV_WHO
    PER_PROPOSAL_QUESTION_MEMB_WHO
    PER_PROPOSAL_QUESTION_TYPE_WHO
    PER_PROPOSAL_TEMPLATES_WHO
    PER_QUALIFICATION_TYPES_WHO
    PER_QUICKPAINT_INVOCATIONS_WHO
    PER_QUICKPAINT_RESULT_TEXT_WHO
    PER_RATING_LEVELS_WHO
    PER_RATING_SCALES_WHO
    PER_RECRUITMENT_ACTIVITIES_WHO
    OBJECT_NAME
    PER_RECRUITMENT_ACTIVITY_F_WHO
    PER_REQUISITIONS_WHO
    PER_RI_DEPENDENCIES_WHO
    PER_RI_REQUESTS_WHO
    PER_RI_SETUP_SUB_TASKS_WHO
    PER_RI_SETUP_TASKS_WHO
    PER_RI_VIEW_REPORTS_WHO
    PER_RI_WORKBENCH_ITEMS_WHO
    PER_ROLES_WHO
    PER_SCHED_COBRA_PAYMENTS_WHO
    PER_SECONDARY_ASS_STATUSES_WHO
    OBJECT_NAME
    PER_SECURITY_ORGANIZATIONS_WHO
    PER_SECURITY_PROFILES_WHO
    PER_SECURITY_USERS_WHO
    PER_SHARED_TYPES_WHO
    PER_SOLUTION_TYPES_WHO
    PER_SPINAL_POINT_PLACEMENT_WHO
    PER_STANDARD_HOLIDAYS_WHO
    PER_TIME_PERIODS_WHO
    PER_TIME_PERIOD_RULES_WHO
    PER_WORK_INCIDENTS_WHO
    PER_ZA_AREAS_OF_ASSESSMENT_WHO
    OBJECT_NAME
    PER_ZA_QUALIFICATION_TYPES_WHO
    PER_ZA_TRAINING_WHO
    PQH_ATTRIBUTE_RANGES_WHO
    PQH_BDGT_CMMTMNT_ELMNTS_WHO
    PQH_BUDGET_DETAILS_WHO
    PQH_BUDGET_ELEMENTS_WHO
    PQH_BUDGET_FUND_SRCS_WHO
    PQH_BUDGET_GL_FLEX_MAPS_WHO
    PQH_BUDGET_POOLS_WHO
    PQH_BUDGET_SETS_WHO
    PQH_COPY_ENTITY_CONTEXTS_WHO
    OBJECT_NAME
    PQH_COPY_ENTITY_FUNCTIONS_WHO
    PQH_COPY_ENTITY_TXNS_WHO
    PQH_CORPS_DEFINITIONS_WHO
    PQH_DE_CASE_GROUPS_WHO
    PQH_DE_ENT_MINUTES_WHO
    PQH_DE_OPERATION_GROUPS_WHO
    PQH_DE_RESULT_SETS_WHO
    PQH_DE_WRKPLC_VLDTN_JOBS_WHO
    PQH_DE_WRKPLC_VLDTN_LVLNUM_WHO
    PQH_DE_WRKPLC_VLDTN_VERS_WHO
    PQH_DFLT_BUDGET_ELEMENTS_WHO
    OBJECT_NAME
    PQH_DFLT_BUDGET_SETS_WHO
    PQH_DOCUMENT_ATTRIBUTES_F_WHO
    PQH_ELEMENT_COMMITMENTS_WHO
    PQH_FR_GLOBAL_INDICES_F_WHO
    PQH_FR_STAT_SITUATION_RULE_WHO
    PQH_FR_VALIDATIONS_WHO
    PQH_GL_INTERFACE_WHO
    PQH_PROCESS_LOG_WHO
    PQH_ROLE_INFO_TYPES_WHO
    PQH_SS_STEP_HISTORY_WHO
    PQH_TABLE_ROUTE_WHO
    OBJECT_NAME
    PQH_TEMPLATES_WHO
    PQH_TEMPLATE_ATTRIBUTES_WHO
    PQH_TJR_SHADOW_WHO
    PQH_TRANSACTION_CATEGORIES_WHO
    PQH_TRANSACTION_TEMPLATES_WHO
    PQH_TXN_CATEGORY_ATTRIBUTE_WHO
    PQH_TXN_CATEGORY_DOCUMENTS_WHO
    PQH_TXN_JOB_REQUIREMENTS_WHO
    PQH_WIZARD_CANVASES_WHO
    PQH_WORKSHEETS_WHO
    PQH_WORKSHEET_BDGT_ELMNTS_WHO
    OBJECT_NAME
    PQH_WORKSHEET_BUDGET_SETS_WHO
    PQH_WORKSHEET_DETAILS_WHO
    PQH_WORKSHEET_FUND_SRCS_WHO
    PQH_WORKSHEET_PERIODS_WHO
    PQP_ALIEN_STATE_TREATIES_F_WHO
    PQP_ALIEN_TRANSACTION_DATA_WHO
    PQP_ANALYZED_ALIEN_DATA_WHO
    PQP_ANALYZED_ALIEN_DETAILS_WHO
    PQP_ASSIGNMENT_ATTRIBUTES_WHO
    PQP_CONFIGURATION_VALUES_WHO
    PQP_EXCEPTION_REPORTS_WHO
    OBJECT_NAME
    PQP_EXCEPTION_REPORT_GROUP_WHO
    PQP_EXCEPTION_REPORT_SUFFI_WHO
    PQP_EXTRACT_ATTRIBUTES_WHO
    PQP_EXT_CROSS_PERSON_RECOR_WHO
    PQP_GAP_ABSENCE_PLANS_WHO
    PQP_GAP_DAILY_ABSENCES_WHO
    PQP_PENSION_TYPES_F_WHO
    PQP_SERVICE_HISTORY_PERIOD_WHO
    PQP_VEHICLE_ALLOCATIONS_F_WHO
    PQP_VEHICLE_DETAILS_WHO
    PQP_VEHICLE_REPOSITORY_F_WHO
    OBJECT_NAME
    PQP_VEH_ALLOC_EXTRA_INFO_WHO
    PQP_VEH_ALLOC_INFO_TYPES_WHO
    PQP_VEH_REPOS_EXTRA_INFO_WHO
    PQP_VEH_REPOS_INFO_TYPES_WHO
    PAY_EXTERNAL_ACCOUNTS_ARUD
    PAY_ORG_PAYMENT_METHODS_F_ARIU
    PAY_US_EMP_STATE_TAX_RULES_WHO
    PER_PHONES_WHO
    PER_TIME_PERIOD_TYPES_WHO
    HXC_ALIAS_DEFINITION012501_WHO
    OTA_ACTIVITY_DEFINIT012501_WHO
    OBJECT_NAME
    OTA_ACTIVITY_VERSION012509_WHO
    HXC_TRANSACTION_DETAILS_BK_WHO
    OTA_OFFERINGS_TL012523_WHO
    HRI_ARCHIVE_EVENTS_WHO
    OTA_SUPPLIABLE_RESOU012528_WHO
    BEN_ACTN_TYP_TL012642_WHO
    DT_DATE_PROMPTS_TL012652_WHO
    DT_TITLE_PROMPTS_TL012653_WHO
    BEN_CM_TYP_F_TL012655_WHO
    GHR_COMPL_AGENCY_COSTS_WHO
    GHR_MASS_SALARY_CRITERIA_E_WHO
    OBJECT_NAME
    GHR_MTS_TEMP_WHO
    HR_ALL_ORGANIZATION_012716_WHO
    HR_ALL_POSITIONS_F_T012716_WHO
    HR_FORM_CANVASES_TL012728_WHO
    HR_FORM_DATA_GROUPS_012729_WHO
    BEN_EXT_FLD_TL012730_WHO
    HR_FORM_ITEMS_TL012730_WHO
    HR_FORM_TAB_PAGES_TL012731_WHO
    HR_FORM_TEMPLATES_TL012732_WHO
    HR_FORM_WINDOWS_TL012733_WHO
    HR_ITEM_PROPERTIES_T012734_WHO
    OBJECT_NAME
    HR_KI_HIERARCHIES_TL012736_WHO
    BEN_LER_F_TL012736_WHO
    HR_KI_INTEGRATIONS_T012736_WHO
    HR_KI_OPTION_TYPES_T012737_WHO
    HR_KI_TOPICS_TL012738_WHO
    HR_NAVIGATION_UNITS_012740_WHO
    HR_ORG_INFORMATION_T012741_WHO
    HR_TAB_PAGE_PROPERTI012748_WHO
    BEN_RPTG_GRP_TL012758_WHO
    PAY_CUSTOM_RESTRICTI012802_WHO
    PAY_ORG_PAYMENT_METH012813_WHO
    OBJECT_NAME
    PER_ASSIGNMENT_STATU012832_WHO
    PER_COMPETENCES_TL012842_WHO
    PAY_ACTION_PARAMETERS_ARI
    PAY_ACTION_PARAMETERS_ARU
    PA_MAITN_ORG_UPDATE_BEST
    PA_MAITN_ORG_UPDATE_BEROW
    JA_IN_57F4_FORM_NUMBER_AIU_TRG
    XXXX_APPS_LOGON_TRG
    767 rows selected.

  • Great speeds wired, poor wireless..

    Good morning.
     I had BT infinity installed earlier this week, absolutely delighted thus far with download speeds nearing 80mb via ethernet connection. However whenever I try using the wifi connection I'm only managing speeds ranging from 4mbs-20mbs.
     I have read numerous posts regarding the adaptor needs upgrading/updating. I honestly have no idea about this and need abit of help in what I need to buy/do in order to achieve greater speeds wireless.
    I have read something about a "N" adaptor. Is this like a usb stick which plugs into the laptop or do you need to take the whole laptop apart and remove the original adaptor? Where can I pick up one of these adaptors and finally how do I find my current adaptor type?
     Sorry for all the questions, i'm absolutely usless with computers.
     Thanks for your time
    James

    Its not usually practical to change the internal wireless card in your laptop, as there can be incompatibility issues, as it depends on the laptops motherboard manufacturer. There is also a chance of damaging the laptop.
    An external USB adapter simply plugs int a spare USB port on the laptop, and you then select that adapter instead of the laptops internal one.
    Here is the TP-Link TL-WN722N as an example.
    There is also a very tiny Edimax EW-7811Un one, which I use myself, and looks like this
    When it is plugged into a USB port, you hardly notice it.
    There are some useful help pages here, for BT Broadband customers only, on my personal website.
    BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

  • DRI (declarative referential integrity) and speed improvements.

    EDITED: See my second post--in my testing, the relevant consideration is whether the parent table has a compound primary key or a single primary key.  If the parent has a simple primary key, and there is a trusted (checked) DRI relation
    with the child, and a query requests only records from the child on an inner join with the parent, then sql server (correctly) skips performing the join (shown in the execution plan).  However, if the parent has a compound primary key, then sql server
    performs a useless join between parent and child.   tested on sql 2008 r2 and denali.  If anyone can get sql server NOT to perform the join with compound primary keys on the parent, let me know.
    ORIGINAL POST: I'm not seeing the join behavior in the execution plan given in the link provided (namely that the optimizer does not bother performing a join to the parent tbl when a query needs information from the child side only AND
    trusted DRI exists between the tables AND the columns are defined as not null).  The foreign key relation "is trusted" by Sql server ("is not trusted" is false), but the plan always picks both tables for the join although only one is needed. 
    If anyone has comments on whether declarative ref integrity does produce speed improvements on certain joins, please post.  thanks.
    http://dinesql.blogspot.com/2011/04/does-referential-integrity-improve.html

    I'm running sql denali ctp3 x64 and sql 2008 r2 x64, on windows 7 sp1. I've tested it on dozens of tables, and I defy anyone to provide a counter-example (you can create ANY parent table with two ints as a composite primary key, and then a child table using
    that compound as a foreign key, and create a trusted dri link between them and use the above queries I posted)--any table with a compound foreign key relation as the basis for the DRI apparently does not benefit from referential integrity between those tables
    (in terms of performance). Or to be more precise, the execution plan reveals that sql server performs a costly and unnecessary join in these cases, but not when the trusted DRI relation between them is a single primary key. If anyone has seen a different result,
    please let me know, since it does influence my design decisions.
    fwiw, a similar behavior is true of sql server's date correlation optimization: it doesn't work if the tables are joined by a composite key, only if they are a joined by a single column:
    "There must be a single-column
    foreign key relationship between the tables. "
    So I speculate, knowing absolutely nothing, that there must be something deep in the bowels of the engine that doesn't optimize compound key relations as well as single column ones.
    SET ANSI_NULLS ON
    GO
    SET QUOTED_IDENTIFIER ON
    GO
    CREATE TABLE [dbo].[parent](
    [pId1] [int] NOT NULL,
    [pId2] [int] NOT NULL,
    CONSTRAINT [PK_parent] PRIMARY KEY CLUSTERED
    [pId1] ASC,
    [pId2] ASC
    )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
    ) ON [PRIMARY]
    GO
    CREATE TABLE [dbo].[Children](
    [cId] [int] IDENTITY(1,1) NOT NULL,
    [pid1] [int] NOT NULL,
    [pid2] [int] NOT NULL,
    CONSTRAINT [PK_Children] PRIMARY KEY CLUSTERED
    [cId] ASC
    )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
    ) ON [PRIMARY]
    GO
    ALTER TABLE [dbo].[Children] WITH CHECK ADD CONSTRAINT [FK_Children_TO_parent] FOREIGN KEY([pid1], [pid2])
    REFERENCES [dbo].[parent] ([pId1], [pId2])
    ON UPDATE CASCADE
    ON DELETE CASCADE
    GO
    /* the dri MUST be trusted to work, but it doesn't work anyway*/
    ALTER TABLE [dbo].[Children] CHECK CONSTRAINT [FK_Children_TO_parent]
    GO
    /* Enter data in parent and children */
    select c.cId FROM dbo.Children c INNER JOIN Parent p
    ON p.pId1 = c.pId1 AND p.pId2 = c.pId2;
    /* Execution plan will be blind to the trusted DRI--performs the join!*/

  • Qt 4.6 Speed improvements

    http://qt.nokia.com/about/news/nokia-releases-qt-4.6
    Im telling about the part which tells "More horsepower"
    Does anyone already tried Qt 4.6 and felt the speed improvement

    mcsaba77 wrote:
    Adriano ML wrote:
    KDE 4.3 is butter smooth on my 1GB Athlon 64 939, geforce 7600GS. Be it with or without kwin composition. My aton with GMA 950 fares really well too.
    Can't wait for QT 4.6 and KDE 4.4
    I second that, I dunno how can anyone describe KDE 4.3.x as slow, unless something is seriously broken in the installation, or if there are driver problems...
    As to ram usage, mine eats 14% of total RAM (I have 2 GB, so that's <300Mb) after start up (and yes, I wait for all services to load, in fact System Load Viever shows only 12% at first), which is ridiculously low considering all the services it provides. I mean KDE is not fluxbox, and yes, I have everything that's needed for a rich desktop experience running in the background (wicd, hal, cups, pulseaudio, kdm, etc.).  I also have 2 desktops with different wallpapers and widgets on each, plus I have desktop effects enabled.
    That really depends upon the system as well.
    For example, I can run KDE (vanilla) on my old p4 1.6 ghz computer with an nvidia geforce 2 agp video card and 1 gb ram. It runs, and as long as i am not trying to do too much it's cpu usage stays around 25%. I can even use kopete on it and do some light browsing. But eventually it stars to slow down as CPU usage races up amongst other things. I 'can' enable compositing effects but that slows tings down even more until eventually it freezes or kde disables it automatically. Thus I am using fluxbox for that computer.
    On my wife's pentium dual core 1.6 gig laptop with 2 gig ram, kde(mod) runs perfectly fine and is fast and able to handle xp in virtual mode with no real problems and with compositing effects on. Occasionally though it does swap when running virtualbox xp and other programs. But other than that, it is running as fast (after the inital load) as fluxbox on my much lder desktop.
    I do suspect that once I get my new machine built in march, that I will be able to enjoy KDE with much greater speeds on it. But it just goes to show you, that on older computers KDE does not feel fast and does feel heavy. Also there is something to be said about not having your DE automatically using up 300-400 MB and loading it's inital settings within a mere second, leaving much more free memory to load other programs faster. But I do also agree that on the latest and greatest machines out there now, unless you are really watching the memory usages like a hawk and timing everything with a nanosecond stopwatch, you probably wouldn't notice the differences in app loading speeds on kde or a lighter environment like fluxbox. Infact you may notice that kde loads kde apps faster than fluxbox loads kde apps (especially true if you use preloading).

  • Have speed improvements been made?

    I just want to say that my posts on the forums today have appeared in the topic list nearly instantaneously — which wasn't the case just a few days ago. And if the forum administrators have made speed improvements recently, but are disappointed no-one has noticed, then perhaps this will bring a modicum of satisfaction.
    ...I wonder if someone "in the know" (Eric?) can indicate whether this is a permanent improvement. If it's merely due to draining the _internet tubes_, it may not be...

    Thanks for your reply, but I'm not sure it explains the particular slow-down I'm seeing...
    Displaying forums is as fast as ever, as is the system's acceptance of new posts/replies. The problem is, as I said, that +"posts take a long time to appear"+. ...I list the main forum page and expect to see my just-accepted post at the top of the list, but it doesn't appear for between one and a few minutes after my post has been accepted. Yes, there's a warning to expect a delay, but I'm pointing out that these forums go through periods of near instantaneous appearance of new posts (as was the case a week ago) to a now sluggish appearance of new posts.
    The idea that there is a geographic aspect to the problem is perhaps nullified by the comment by MGW (in New Hampshire?) above:
    "Actually, the speedup has been noticeable for the past couple of days, having complained bitterly about the clog..."
    Also during "clogged" periods, duplicate posts from all over the world tend to appear as members mistakenly think their post, although accepted by the system, didn't "take" and re-enter it — because it doesn't show up in the forum's main list for a couple of minutes or so.
    ...We seem to regularly go through these alternating multi-week periods of members reporting speed and sluggishness but, so far, with no acknowledgement or explanation from the hosts.
    By the way, this post itself took a minute to appear in the main forum list — a week ago, it would have appeared almost instantaneously.
    Message was edited by: Alancito

  • Speed improvements in JDeveloper 3.0

    Will the overall response time/speed improve in JDeveloper 3.0?
    Thanks
    Mike
    null

    Hi
    JDeveloper 3.0 is in beta right now, and it has improvements in
    response time/speed.
    For example the deployment wizard is way faster.
    regards
    raghu
    Michael Maculsay (guest) wrote:
    : Will the overall response time/speed improve in JDeveloper 3.0?
    : Thanks
    : Mike
    null

  • Great DOT improvement using Bios 3.6 for 865PE Neo-2 P series

    Great DOT improvement of Bios 3.6O for 865PE Neo-2 P series.
    Thanks to NovJoe and everybody in the following thread (especially iliveonhope)
    https://forum-en.msi.com/index.php?sid=&postid=277300#post277300
    The DOT is kind like straight forward approach by reaching the preset DOT on the bios after booting and during aplication for less then 2 second, the old bios is gradually increasing almost 1 minute or more.
    Also the FSB reading on CC is function well not randomly change as on the last Bios.
    The Autooverclocking value using CC if not change by default is always shown the maximum FSB.
    The weaknesess is still the default value using 'save' on CC  that not performing well (its better to have user define FSB value) and also the DOT range could be much higher then the Commander so I can set certain FSB value to max FSB value. (Waiting for the next improvement from the MSI Software Team).
    It will work fine for anybody who use FSB:DRAM Feq. = 1:1 using DDR greater then 400
    Interesting thing about this DOT method is it always back on the lowest FSB during stand-by, for me its great hardware saving (It will be great if the FSB stays on the user define setting).
    Regarding the CPU temperatue is a little bit lower compared with the 865PE Neo-2 S series using the same Heat sink type.
    Its worth to try except it cannot reach the maximum OCing due to the DOT rank limitation.
    M/B 865 PE Neo-2 PFS Platinum Edition Bios Ver.3.6
    CPU:P4 2.4C (HT enable) and ThermalTake SubZero 4G
    (Commander,Turbo,2434 mHz - 2760 mHz)
    Memory: Corsair XMS 3500 2x512 meg (dual-channel dimm 2 and 4) 2-3-2-5
    VGA:ELSA Gladiac 925 Ti4600
    HD:2 SATA Maxtor 80gig and 1 ATA Maxtor 80Gig
    CD/RW Yamaha and Pioneer DVD
    PSU:ThermalTake Silent PurePower 480W (W0010/Black)
    +5 V/40 A, +3.3 V/30 A, +12 V/18 A, -5 V/0.3 A, -12 V/0.8 A, +5 VSB/2 A Peak Load 550 W
    Window XP SP1
    NEC FP2141SB
    Microsoft DesktopPro
    Sound Blaster Audigy 2 Platinum + Klipsch Promedia 4.1

    clausman,
    What bios version do you used ? is already version 3.6
    If you are using Bios 3.60 try to run PC mark 2002 or other benching software (if you have it), you will note that when the benchmark starting the FSB will raise and then after you stop it in the middle or end the FSB will go back to the lowest FSB (Do it by showing the CC beside the PC mark.
    Please let me know.
    M/B 865 PE Neo-2 PFS Platinum Edition Bios Ver.3.6
    CPU:P4 2.4C (HT enable) and ThermalTake SubZero 4G
    (Commander,Turbo,2434 mHz - 2760 mHz)
    Memory: Corsair XMS 3500 2x512 meg (dual-channel dimm 2 and 4) 2-3-2-5
    VGA:ELSA Gladiac 925 Ti4600
    HD:2 SATA Maxtor 80gig and 1 ATA Maxtor 80Gig
    CD/RW Yamaha and Pioneer DVD
    PSU:ThermalTake Silent PurePower 480W (W0010/Black)
    +5 V/40 A, +3.3 V/30 A, +12 V/18 A, -5 V/0.3 A, -12 V/0.8 A, +5 VSB/2 A Peak Load 550 W
    Window XP SP1
    NEC FP2141SB
    Microsoft DesktopPro
    Sound Blaster Audigy 2 Platinum + Klipsch Promedia 4.1

  • On an IMac will a 4GB graphics card give a noticeable speed improvement over a 2GB card?

    On an IMac will a 4GB graphics card give a noticeable speed improvement over a 2GB card?

    In terms of Lightroom I'm pretty sure the answer would be "no".

  • Site Speed Improvements

    To All:
    I am looking for ways to improve my website loading speed. I have several albums on the site (www.lens-perspective.com) and I am wondering...
    1.) if the site would load faster if limited my albums to 10-15 pictures.
    2.) Should I optimize the pictures for the web myself instead of letting iWeb do it?
    2.) Also, instead of using the ALBUM Template page in iWeb, am I better of using a blank page and placing one picture on it for each album and then hyperlinking to each album from that page?
    3.) Lastly, there should be 2 pictures on my "About Me" page and they don't seem to load after my site is uploaded. Do you think that this is a browser issue? I host the site at GO Daddy and upload it using Fetch.
    Any other "speed" recommendations are welcome.
    Thank you,
    Randy

    1. Yes. Large albums take much longiing to load and keeping the albums under 15 images is a good idea.
    2. Probably not worth the time and effort. Your current files average about 100 KB's (good size for Web use). 15 on a page would be 1.5 MB's that needs to download.
    3. I see three images on the About Me page. One large and two smaller (lower part of the page).

  • Will URLS (Unified light speed) improves the current app. perf. as well ?

    Hi,
    We are using ABAP webdynpro application that encapsulates Interactive PDF as well. But it's performance is not good.
    Normally it takes 30-50 seconds when user opens the workitem from UWL which further calls the webdynpro application and shows the pdf to user.
    My question is if we go for EHP1 for NW that will give Unified Rendering Light Speed in Web Dynpro ABAP  then will this technology helps to improve the current webdynpro application performance or only the new applications that will be built using this.
    Please suggest me for this or tell me the other way to improve the performance of webdynpro application.
    Thanks,
    Rahul

    Hi Rahul,
    The new light speed rendering engine is the rendering framework to render the Webdynpro applications. Therefore there is nothing where by you specify that a particular application is developed using the Light speed rendering engine.
    In other words to answer your question, EHP1 will improve the performance for all the applications whether developed on EHP1 or developed prior to EHP1.
    Regards
    Rohit Chowdhary

  • MacBook Pro vs iMac - speed improvement for Parallels Windows 8.1

    Will there be a noticeable increase in speed and performance in switching from an iMac 2.9GHz quad-core Intel Core i5 with 1TB HardDrive to a MacBook Pro - Retina Display 13-inch 2.6GHz dual-core Intel Core i5 with 512 SSD.??? Both being brand new iMac and MacBook Pro.
    I am not sure if the SSD drive will make a noticeable difference in this scenario. I am trying to investigate if doing the switch will make the use of Parallels with Windows 8.1 better; the iMac seems to be dragging a bit while running Windows through Parallels.
    Thanks,

    I would be looking at the Quad core MBP for Parallels. A Quad-core vs Dual-Core is not a fair comparison.
    For the same CPU, the two bottlenecks for Parallels are RAM and disk speed.
    You will see an improvement if you max out the RAM and the disk speed. The SSD in the MBP will be much faster than the HDD in the iMac.

  • LabVIEW MathScript computation speed improvement

    I am using a MathScript node to make calculations on an sbRIO FPGA module and the speed of these computations is critical.  What are some ways to improve the speed of calculations and is there a faster way to do matrix calculations than MathScript?  If I make the MathScript portion into a subVI will it improve the speed of calculations?
    Thanks for any ideas
    Solved!
    Go to Solution.

    Please look at the attached VI. It has your original .m code, my modifications to your .m code, and the G code equivalent to the modified .m code. First, let me describe to you the numbers I saw on a cRIO 9012 for each of the three approaches.
    I ran each of the three approaches for hundred iterations, ignored the first 30 iterations to allow for memory allocations (which caused a huge spike in run-time performance on RT), and then took the average run-time for each loop iteration for the remaining iterations
    Original M: 485 msec/iteration
    Modified M: 276 msec/iteration
    G: 166 msec/iteration
    The modifications I made to your .m code are the following:
    (1) Added ; to end of each line to suppress output (used for debugging)
    (2) Moved the random code generation out - used whitenoise (seems like that's what you were doing)
    (3) Switch on the data type highlighting feature. Noticed that majority of the data was casted to complex, although didn't seem like you needed the complex domain. The source was sqrt function. Modified it to using real(sqrt(...))
    This improved performance by over 40%. I believe more can be squeezed if you follow the documentation - Writing MathScript for Real-Time Applications. 
    Then, I took the MathScript you had and wrote equivalent G leaving the algorithm as is. This gave us performance improvement of another 40% over the modified G. This is a known issue that on slow controllers MathScript adds a 2x penalty to equivalent G. We are currently investigating this issue and may be able to fix it in a future release.
    If you profile the G code, you will notice that most of the time is spent in matrix multiplication. Unless you rethink your algorithm, I doubt this can improve further.
    Let me know if you have questions
    Regards,
    Rishi Gosalia
    Attachments:
    Mathcript_efficiencyProblem Modified.vi ‏255 KB
    MathScript_efficiencyProblem_G.vi ‏62 KB

  • Would upgrading my internet speed improve Netflix performanc​e?

    I know there is a lot of controversy surrounding netflix and ISPs which I'm not really interested in. I just know my netflix streaming is terrible right now and I would be willing to upgrade my internet speed if it meant that would improve. Any idea if it would? Thank you/

    NO! Don't do it.
    You'll just be throwing more money at Verizon with no change in performance. Realistically you could probably downgrade your speed, save yourself money, and see no change in your Netflix performance.

Maybe you are looking for