مشكلة أداء خدمة الويب

Question

لدي خدمة ويب ASMX بسيطة تحتاج فقط إلى تسجيل بعض المعلومات في قاعدة بيانات للمعاملات.ومع ذلك فقد حان الوقت للعميل.استدعاء تحديث قاعدة البيانات يستدعي الإجراء 1 المخزن فقط ولا أصدق أنه يمكن تحسينه بشكل أكبر للحصول على أداء أفضل.لقد اختصرت فقط لتسجيل التشغيل باستخدام log4net ثم قراءة تسجيل الدخول من خلال عملية منفصلة لتحديث قاعدة البيانات.

كنت أتساءل عما إذا كانت هناك طريقة أفضل للقيام بذلك.كنت أتساءل عما إذا كانت هناك طريقة لجعل الكود الخاص بي يفعل شيئًا مثل: Genacodicetagpre

Answer 1

EDIT: I was wrong about BackgroundWorker. So I chaged it to the Thread version, tested.

If you want the work done asynchronously, you can study how to start another thread.

public class Service1 : System.Web.Services.WebService
{

    [WebMethod]
    public void Log(int foo, int bar)
    {
        Thread a = new Thread(new ThreadStart(delegate()
        {
            // Do some processing here
            // For example, let it sleep for 10 secs
            Thread.Sleep(10000);
        }));
        a.Start();
    }
}

It would take 10 seconds for Log method to finish processing if the Thread.Sleep(10000) line is in the Log method itself. However, with Thread a, The Log method will return immediately after call.

Also note that, there is no easy way to guarantee the calling client if the insert operation is completed or not, with this style of asynchronous call.

Answer 2

One thing you may want to try is Tracing.

Answer 3

If the query cannot be optimized any further you could increase the timeout value for your SQL client assuming you might be using SQL server.

On the client side that consumes the web service, you can use that method asynchronously if you would like the client to continue performing other operations. When the web method is finished it will trigger an event. There is a nice little example you can read here if you think it might help.

Answer 4

While you can look at doing asynchronous operations inside your webmethod, you're working with threads and/or the threadpool inside asp.net, which already has multi-threading operations in play. While technically feasible, you can also inadvertently rob the system of resources as the httpruntime manages resources in serving requests to your service.

Writing to the local log4net file and importing that data in an offline routine is higher availability than real-time logging, asynch or otherwise, since your sql server can be offline and your service is still available. If you don't require sql server for anything other than logging, prefer keeping db operations out of the webmethod.

Answer 5

If it's just a fire-and-forget call for the client, your web service could just add the details to a queue and return to the client. I've used MSMQ to implement something similar to what you're describing. It doesn't fix a database timeout but it does take the error message away from your clients.