Hi Paul A good explanation -- I think you fall into the category of "understands the guard rails" :)
I'm glad you found that fragmentation was a good answer and that it worked so well. Charles ________________________________ From: general-boun...@developer.marklogic.com [general-boun...@developer.marklogic.com] on behalf of Paul Vanderveen [pvanderv...@terraxml.com] Sent: Thursday, September 08, 2016 8:30 AM To: MarkLogic Developer Discussion Subject: Re: [MarkLogic Dev General] General Question about Documents and Fragments Charles, thanks for the response. That makes sense that we’re looking at fragments and properties. I completely understand your comments about fragmenting and why MarkLogic is taking the stance that you should not use it. If we were starting from scratch I would absolutely load separate documents. In our environment, however, that meant spending months to refactor a large amount of queries and backend code, test, then convert and update a large amount of legacy data at our customer site. Our data is very flat and lends itself well to fragmenting, so we gave it a try. The addition of fragmenting was a huge instant win as it improved performance at least 10x on larger manuals with virtually no changes to code or existing data. It also virtually eliminated expanded tree cache errors that were becoming frequent. In our particular case it was the best option, and so far we’ve found very little downside to it. I’d love to see us be able to refactor in the future to smaller docs, but our customers are very happy to see blisteringly fast performance today. Guidelines are good, but sometimes you just gotta cross the beams
_______________________________________________ General mailing list General@developer.marklogic.com Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
