I am new to DFP. I am trying to show an image from collection of images to a single slot with time interval of 5 sec. What i found is some images get display in 5sec and some came and changes within 2 or 3 sec. This inconsistency looks very ugly. I tried to debug with google force console and found this logs :
Status Time Description
Information Start Created slot: /116095010/marcom_0
Information 1 ms Google service JS loaded
Information 1 ms Created service: publisher_ads
Information 2 ms Associated service "publisher_ads" with slot "/116095010/marcom".
Information 2 ms Invoked queued function. Total: 1. Errors: 0.
Information 2 ms Setting targeting attribute user_state with value visitor for service publisher_ads
Information 2 ms Setting targeting attribute utm_source with value dfp for service publisher_ads
Information 2 ms Setting targeting attribute utm_campaign with value Nag_StartMyFreeTrial_Desktop_min for service publisher_ads
Information 2 ms Setting targeting attribute utm_medium with value internalcpc for service publisher_ads
Information 2 ms Setting targeting attribute undefined with value 20500102 for service publisher_ads
Information 2 ms Using asynchronous rendering mode to fetch ads.
Warning 3 ms **The ads cannot be refreshed because the GPT implementation Javascript is not yet loaded.**
Information 4 ms GPT implementation fetched.
Information 8 ms Calling fillslot.
Information 34 ms Fetching ad for slot: /116095010/marcom
Information 46 ms Invoked queued function. Total: 1. Errors: 0.
Information 432 ms Receiving ad for slot: /116095010/marcom
Information 433 ms Rendering ad for slot: /116095010/marcom
Information 433 ms Completed rendering ad for slot: /116095010/marcom
Information 824 ms Created slot: /116095010/collection-carousel-top-desktop_0
Information 824 ms Associated service "publisher_ads" with slot "/116095010/collection-carousel-top-desktop".
Information 824 ms Invoked queued function. Total: 2. Errors: 0.
Information 824 ms Setting targeting attribute user_state with value visitor for service publisher_ads
Information 824 ms Setting targeting attribute utm_source with value dfp for service publisher_ads
Information 824 ms Setting targeting attribute utm_campaign with value Nag_StartMyFreeTrial_Desktop_min for service publisher_ads
Information 824 ms Setting targeting attribute utm_medium with value internalcpc for service publisher_ads
Information 824 ms Setting targeting attribute undefined with value 20500102 for service publisher_ads
Information 824 ms Using asynchronous rendering mode to fetch ads.
Information 824 ms Refreshing ads.
Information 870 ms Fetching ad for slot: /116095010/marcom
Information 871 ms Service is already enabled
Information 871 ms Calling fillslot.
Information 881 ms Invoked queued function. Total: 2. Errors: 0.
Information 905 ms Created slot: /116095010/collection-carousel-top-desktop_1
**Error 905 ms Div element div-gpt-ad-1440572949275-0 is already associated with another slot.
Error 905 ms Exception when invoking function: Cannot read property 'addService' of null**
Information 905 ms Invoked queued function. Total: 2. Errors: 1.
Information 905 ms Setting targeting attribute user_state with value visitor for service publisher_ads
Information 905 ms Setting targeting attribute utm_source with value dfp for service publisher_ads
Information 905 ms Setting targeting attribute utm_campaign with value Nag_StartMyFreeTrial_Desktop_min for service publisher_ads
Information 905 ms Setting targeting attribute utm_medium with value internalcpc for service publisher_ads
Information 905 ms Setting targeting attribute undefined with value 20500102 for service publisher_ads
Information 905 ms Using asynchronous rendering mode to fetch ads.
Information 905 ms Refreshing ads.
Information 953 ms Service is already enabled
Information 953 ms Calling fillslot.
Information 955 ms Invoked queued function. Total: 2. Errors: 1.
Information 961 ms Created slot: /116095010/NAG-Visitor-desktop_0
Information 961 ms Associated service "publisher_ads" with slot "/116095010/NAG-Visitor-desktop".
Information 961 ms Invoked queued function. Total: 3. Errors: 1.
Information 961 ms Setting targeting attribute user_state with value visitor for service publisher_ads
Information 961 ms Setting targeting attribute utm_source with value dfp for service publisher_ads
Information 961 ms Setting targeting attribute utm_campaign with value Nag_StartMyFreeTrial_Desktop_min for service publisher_ads
Information 961 ms Setting targeting attribute utm_medium with value internalcpc for service publisher_ads
Information 961 ms Setting targeting attribute undefined with value 20500102 for service publisher_ads
Information 961 ms Using asynchronous rendering mode to fetch ads.
Information 961 ms Refreshing ads.
Information 962 ms Service is already enabled
Information 962 ms Calling fillslot.
Information 973 ms Invoked queued function. Total: 3. Errors: 1.
Information 1273 ms Receiving ad for slot: /116095010/marcom
Information 1273 ms Rendering ad for slot: /116095010/marcom
Information 1273 ms Completed rendering ad for slot: /116095010/marcom
Information 1277 ms Fetching ad for slot: /116095010/collection-carousel-top-desktop
Information 1730 ms Receiving ad for slot: /116095010/collection-carousel-top-desktop
Information 1730 ms Rendering ad for slot: /116095010/collection-carousel-top-desktop
Information 1730 ms Completed rendering ad for slot: /116095010/collection-carousel-top-desktop
Information 1733 ms Fetching ad for slot: /116095010/marcom
Information 2095 ms Receiving ad for slot: /116095010/marcom
Information 2095 ms Rendering ad for slot: /116095010/marcom
Information 2095 ms Completed rendering ad for slot: /116095010/marcom
Information 2099 ms Fetching ad for slot: /116095010/collection-carousel-top-desktop
Information 2488 ms Receiving ad for slot: /116095010/collection-carousel-top-desktop
Information 2488 ms Rendering ad for slot: /116095010/collection-carousel-top-desktop
Information 2488 ms Completed rendering ad for slot: /116095010/collection-carousel-top-desktop
This contain 1 warning and two error. I googled it but not get any help.
I tried to move the refresh code at last of page but that also not help.
Please advise.
Related
Our project has Microsoft Service Bus (on-prem ) running on Windows 2012 R2 servers for message processing.
When sending messages to service bus topic above the size limit (say 10 mb ) , services bus shows processing error – throws socket timeout exception.
Just wanted to know ,
if anyone has worked with sending messages (say > 10 MBs ) to Service Bus Topics . Would appreciate any suggested approach on how to handle this.
Also is there a way to increase the service bus timeout configuration or message size limit settings on Service Bus Topics either through Powershell cmds or Service Bus Explorer.
Service Bus queues support a maximum message size of 256 Kb (the header, which includes the standard and custom application properties, can have a maximum size of 64 Kb).
There is no limit on the number of messages held in a queue but there is a cap on the total size of the messages held by a queue. This queue size is defined at creation time, with an upper limit of 5 GB.
Are you asking about sending a message which is of size 10 MB? Service Bus doesn't allow that large message. For Premium, the maximum message size is 1 MB, and for Standard, it's 256 KB as #Ana said.
Also is there a way to increase the service bus timeout configuration
or message size limit settings?
Yes, there is a possibility to handle time-to-live property of messages which can be configured either at the time of Queue/Subscription creation or while sending Individual message. Refer to set Time to live for Queue as well as message.
Also is there a way to increase message size limit settings?
No, as the maximum size is 1 MB (May be increased by Azure in the future).
To answer this "Can we Send messages (say > 10 MBs ) to Service Bus Topics".
Now as of today, the updated answer will be YES: The Premium tier of Service Bus, enabling Message size up to 100 MB. Where as Standard is up to 256 KB as of today.
How to enabling large messages support for an existing queue (or topic)
Recommended:
While 100 MB message payloads are supported, it's recommended to keep the message payloads as small as possible to ensure reliable performance from the Service Bus namespace.
The Premium tier is recommended for production scenarios.
In chrome 1st request Queued at 0.0 ms and stared at 1 ms but
2nd immediate request queued at 15 s and stared at 10 s. not able to understand why 2nd request start at 10 and Queued at 15 senter image description here where is 5 sec missing. plz help
I implemented exports.get = function(request,response) of a custom api on a mobile service of azure. I download 5 thousands records from the rest service and then i prepare the json for the output. The problem is that the time of downloading of all records is too long, for that script exceeds the default timeout of 30 secs. I was thinking if there is a way to increase the timeout of the response.
I don't believe you can have a timeout greater than 30 seconds, as I have encountered this problem myself with azure custom APIs. According to this link https://msdn.microsoft.com/en-us/library/azure/dd894042.aspx, Table operations are limited to 30 seconds, but it's not clear if that applies to custom apis, but it certainly appears to be.
What I would recommend is to implement pagination and return a limited number of records at a time. Your parameters should include the the start index and amount of records to return, and your response should include how many records in total so you can determine how many records to fetch with each request.
I am doing load testing with an SSRS report and getting more and more disappointed with it.
I need an expert opinion whether there is a way to improve performance.
Environment setup:
SSRS Report which calls stored procedure that selects from table with 5000 rows, runs 3 milliseconds top.
C# Application which based on input parameters creates threads and in parallel makes calls to the SSRS Report.
SSRS is accessed by POST request to the URL and under one NT User.
Stats:
Stored procedure in MSSM Studio runs 3 milliseconds
SSRS report in IE runs for 50ms
C# Application with single thread gets results back in 157 - 239 milliseconds
4 threads average 500 milliseconds for the same report
8 threads: 800 milliseconds for the same report.
16 threads: 1300 milliseconds for the same report.
Is there any configuration or settings that can be changed so SSRS handles concurrent calls better?
Apparently the RS service only has 2 threads available per CPU. I've seen that number touted in various forums around the net, here is one.
You may find that the threads you are attempting to fire up are actually hindering the performance, effectively 'overloading' the RS threads. You can check your log file to see if threads are being stressed according to this, and states you can expect an error of the following type in the log:
WARN: Thread pool pressure. Using current thread for a work item
Perhaps you could look at matching the number of max concurrent threads you are creating to the number of CPUs the RS service has access to * 2
I have below configs on ARMv7 embedded OMAP system.
sched_rt_period_us = 1000000 = 1 sec
sched_rt_runtime_us = 950000 = 0.95 sec
And i have 4 Real time processes running with SCHED_RR and pri = 1
and sched_rr_get_interval () returned 93750000 nanosec, i.e. 0.093750 sec on system.
I have added a new process with SCHED_RR and pri of 1 and same default rr_interval
of 0.09375 sec.
According to this configs:
On every second 5 RT processes must execute 2 times each (0.09375 * 10 = 0.9375 sec) and
rest of the time interval of 1 Sec is to be used by non-RT tasks
i.e., 1.0 - 0.9375 = 0.0625 Sec.
But as i see from execution the 5th newly added task misses the timeline and only executes randomly and produces output every 1 sec or indeterminate. Please help me on how to make
this new process deterministic so that it executes twice per sec as per above configs.
I tried to configure static pri of 2 and also checked with SCHED_FIFO but got the same
results.
Or is there anything i am missing in these calculations.
I am using :
Linux xxxx 2.6.33 #2 PREEMPT Tue Aug 14 16:13:05 CEST 2012 armv7l GNU/Linux
Are you sure that the scheduler does not fail because it is not able to honor the scheduling requests? I mean, that fifth task doesn't meet the deadline because the system is too heavily loaded?
As far as I know, sched_setscheduler does not have a way to signal that the system load is too heavy. To know if the system is able to meet the request, you need another scheduling algorithm, such as edf. Maybe you want to check its implementation for linux.