Have to checked performance with and without the dao to see if it's the
dao or mapper that's causing your issue?  I'm just asking because the
dao in general is deprecated and unless you have some specific design
requirements, the mapper gives you pretty decent database independence
IMHO.

  _____  

From: Kiran Polavarapu [mailto:[EMAIL PROTECTED] 
Sent: Sunday, June 10, 2007 10:00 PM
To: [email protected]
Subject: IBATIS.NET Performance Issues


Hi,

My web application designed with c#,.NET 2.0, MYSQL and IBATIS.NET is
too slow and I just ran the performance profiler and figured out that
the slowest methods in my entire web application are IBATIS methods. 

In the following chunk of code, _daoManager =
ServiceConfig.GetInstance().DaoManager takes 4.0225 seconds to execute.

  public class ArticleService
    {
        #region Fields

        private static readonly ArticleService _instance = new
ArticleService(); 
        private IDaoManager _daoManager = null;
        private IArticleDao _articleDao = null;

        #endregion //Fields

        #region Constructor

        private ArticleService()
        { 
            _daoManager = ServiceConfig.GetInstance().DaoManager;
            _articleDao = (IArticleDao)_daoManager[typeof(IArticleDao)];
        }


Please let me know how to get rid of this and improve performance. 

Thanks,
Kiran. 
--------------------------------------------------------

Princeton Retirement Group, Inc - Important Terms 
This E-mail is not intended for distribution to, or use by, any person or 
entity in any location where such distribution or use would be contrary to law 
or regulation, or which would subject Princeton Retirement Group, Inc. or any 
affiliate to any registration requirement within such location. 
This E-mail may contain privileged or confidential information or may otherwise 
be protected by work product immunity or other legal rules. No confidentiality 
or privilege is waived or lost by any mistransmission. Access, copying or 
re-use of information by non-intended or non-authorized recipients is 
prohibited. If you are not an intended recipient of this E-mail, please notify 
the sender, delete it and do not read, act upon, print, disclose, copy, retain 
or redistribute any portion of this E-mail. 
The transmission and content of this E-mail cannot be guaranteed to be secure 
or error-free. Therefore, we cannot represent that the information in this 
E-mail is complete, accurate, uncorrupted, timely or free of viruses, and 
Princeton Retirement Group, Inc. cannot accept any liability for E-mails that 
have been altered in the course of delivery. Princeton Retirement Group, Inc. 
reserves the right to monitor, review and retain all electronic communications, 
including E-mail, traveling through its networks and systems (subject to and in 
accordance with local laws). If any of your details are incorrect or if you no 
longer wish to receive mailings such as this by E-mail please contact the 
sender by reply E-mail. 

--------------------------------------------------------

Reply via email to