Rajesh,
The fundamentals of that performance argument are sound. However, as Justin 
mentioned, a lot of work has been done to ensure that the search API is highly 
performant. While it is possible that you could write cts search calls that are 
as fast or faster than search:search, to do so would require a great deal of 
sophistication and knowledge of the cts:search Apis and the way MarkLogic 
server works. In general search:search will be much faster for the vast 
majority of users and use cases. 

----
Sent from my iPad

Clark D. Richey, Jr.
Principal Technologist, Federal
MarkLogic
+1 240 252 7507 Cell
[email protected]


1600 Tysons Blvd., 8th Floor
McLean, VA 22102
www.marklogic.com
 
This e-mail and any accompanying attachments are confidential. The information 
is intended solely for the use of the individual to whom it is addressed. Any 
review, disclosure, copying, distribution, or use of this e-mail communication 
by others is strictly prohibited. If you are not the intended recipient, please 
notify us immediately by returning this message to the sender and delete all 
copies. Thank you for your cooperation.

On Mar 30, 2011, at 8:49 AM, "Rajesh Marklogic" <[email protected]> 
wrote:

> Hi Justin,
> 
> Thanks for your reply.
> 
> This is not related to the project tasks. We had casual discussion  on
> Search API Performance and there was an argument that Search:search is
> better than CTS:search.
> 
> I argued that cts:search will be better in terms of performance as
> search:search is built on top of cts api.
> 
> As per your reply, i understood that we can use search:search which
> will not have major performance issues.
> 
> Thanks once again.
> 
> regards
> 
> Rajesh Govindan
> 
> On 3/29/11, Justin Makeig <[email protected]> wrote:
>> Rajesh,
>> Without knowing more about what you’re trying to accomplish, I’d recommend
>> starting with the Search API (or even plain XPath). The Search API is built
>> on top of the core cts libraries and we’ve done a lot of work to make sure
>> it performs at scale. If and when you need to do something more advanced
>> that you can’t easily express in the Search API, it includes built-in
>> extension mechanisms to customize the behavior. Please take a look at the
>> “Search Developer’s Guide”
>> <http://developer.marklogic.com/learn/4.2/search-dev-guide> for more
>> information.
>> 
>> Justin
>> 
>> 
>> 
>> 
>> Justin Makeig
>> Senior Product Manager
>> MarkLogic Corporation
>> 
>> Phone +1 650 655 2387
>> 
>> email  [email protected]<mailto:[email protected]>
>> web    www.marklogic.com<http://www.marklogic.com/>
>> 
>> 
>> 
>> This e-mail and any accompanying attachments are confidential. The
>> information is intended solely for the use of the individual to whom it is
>> addressed. Any review, disclosure, copying, distribution, or use of this
>> e-mail communication by others is strictly prohibited. If you are not the
>> intended recipient, please notify us immediately by returning this message
>> to the sender and delete all copies. Thank you for your cooperation.
>> 
>> On Mar 28, 2011, at 8:41 PM, Rajesh Marklogic wrote:
>> 
>> Hi,
>> 
>> i would like to perform a plain search in mark logic database.  Mark logic
>> provides two search libs/ api i.e Search:Search and CTS:Search.
>> 
>> My search will be executed against particular element (s) or attributes and
>> i am not using search:search api features like highlight, facet etc.,.
>> 
>> The result should contains matched xml documents and total number of records
>> matched.
>> 
>> Please let me know, which api (search:search or cts:search)  will be better
>> in terms of performance and reasons behind that.
>> 
>> Thanks in Advance.
>> 
>> Rajesh
>> _______________________________________________
>> General mailing list
>> [email protected]<mailto:[email protected]>
>> http://developer.marklogic.com/mailman/listinfo/general
>> 
>> 
> _______________________________________________
> General mailing list
> [email protected]
> http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________
General mailing list
[email protected]
http://developer.marklogic.com/mailman/listinfo/general

Reply via email to