Our problem :
We actually loading measures with 2 millions of row by month (there are a lot of dimensions for this measures...). With our actual PMF (5.2.1 HF1), each time we are trying to load, the tool try to match all of the value in MEASURES of the measure series.
So if we have 8 month loaded in PMF, the tool try to HOLD 8 * 2 = 16 millions of rows.
We think that, since the time period is always passed, PMF have to detected the period we're trying to load and the period actually in the tool, and compare ONLY the same period.
We find, that this process is in pmf_meas_look.fex and we read in the "5.2.3 HF2 readme.txt" that a bug was fix in pmf_meas_look.fex.
So are we talking about the same bug ? Because we look at the new pmf_meas_look.fex (5.2.3 HF2) and it seems to talk about that ?
Windows 2008 srv
PMF 5.3.1 HF5
In PMF 5.2.3 HF2 there are a number of enhancements which will speed up measure loading.
One of the things we did was to check the time periods of the incoming data being loaded and use that as a basis for comparison against existing data in PMF.
So if your incoming data has just one month of data - AND - if your load is configured for the standard "Replace Existing data add new" mode, then we will only extract the current month's data from PMF. So in your situation the most we would extract from PMF would be 2M rows.
|Powered by Social Strata|