Project

General

Profile

« Previous | Next » 

Revision 52356

Additional logs to confirm we can and must improve how the result list is prepared and returned to the caller

View differences:

DNetOAICore.java
89 89
		// if the number of records changed, then for sure we can invalidate the resumption token, unless we have a new total of -1 (date
90 90
		// range queries can't be counted for performance reasons)
91 91
		if ((total != -1) && (oldCount != total)) throw new BadResumptionTokenException(resumptionToken);
92

  
92
		long start = System.currentTimeMillis();
93 93
		ListDocumentsInfo res = this.prepareListDocumentsInfo(results, mdf, query, resToken.getRequestedSet(), resToken.getnRead(), resToken.getnMaxElements(),
94 94
				resToken.hasDateRange());
95 95
		res.setCursor(resToken.getnRead());
96
		long end = System.currentTimeMillis();
97
		log.debug("ListDocumentInfo ready in (ms): " + (end - start));
96 98
		return res;
97 99
	}
98 100

  
......
142 144
			UnaryFunction<String, String> function = getLookupClient().getUnaryFunctionFromTDSRule(mdfInfo.getTransformationRuleID());
143 145
			results = store.getRecords(query, function, !onlyIdentifiers, pageSize);
144 146
		}
147
		log.debug("Got cursor");
145 148
		return results;
146 149
	}
147 150

  

Also available in: Unified diff