Starting December 23rd/24th, I have seen a significant *speed up* in the
reporting API responses. Anyone else noticed this? It is still not back to
the pre-September 7 levels, but there is a noticeable 20% or more
improvement. Could the API team do more of this magic that happened? Thanks
:)
On Monday, 11 September 2017 17:01:38 UTC+2, AdWordsApiUser wrote:
>
> Hi Team,
>
> We're noticing a significant slowdown in the throughput of the AWQL
> Reporting using the API since last week, where we're spending about 30%-40%
> more time than usual. Is this a known issue, or something that
Yes, the reporting API is still extremely slow and I doubt anything will
change in near future.
On Monday, December 11, 2017 at 5:32:23 PM UTC+1, Dorian Kind wrote:
>
> Hi all,
>
> I was just wondering whether the situation is still the same for you? On
> our end, the reporting slowdown first
Hi all,
I was just wondering whether the situation is still the same for you? On
our end, the reporting slowdown first encountered in September seems to be
permanent.
Thanks for your feedback and best regards,
Dorian
On Tuesday, 7 November 2017 11:50:10 UTC+1, Tomas R wrote:
>
> It's a bit
It's a bit like a closed loop:
1) Reporting API does not support sorters and paging, so you end up getting
data you don't really need which increases response time.
2) All the requests are super slow anyway, so you have to implement caching
with multi-threading. The slower it gets, the more
Hi Michael,
Any updates on this? It appears that some particular accounts are affected
more badly than others. If I find something specific I will send it across.
Thanks.
MG
On Wednesday, October 18, 2017 at 5:50:42 PM UTC+5:30, Michael Cloonan
(AdWords API Team) wrote:
>
> Hello,
>
> Thanks
Hello,
Thanks for the extra context. I will relay this to the team and I will
share here when I have any updates.
Regards,
Mike, Adwords API Team
On Wednesday, October 18, 2017 at 5:53:17 AM UTC-4, AdWordsApiUser wrote:
>
> I don't have numbers prior to September 7, because we did not do per
I don't have numbers prior to September 7, because we did not do per call
timing tests before the apparent slowdown.
A nightly job, that pulled the same query for many thousand accounts, would
complete by 11AM. Starting September 7, it now runs till 5 PM. Something
happened between Sep 6 and
Hello,
Thanks for the answers to my questions, AdWordsApiUser. For the last
question, can you give the real-time it takes to run reports previously and
now, rather than just how much slower it is relatively to before?
Regards,
Mike, AdWords API Team
On Tuesday, October 17, 2017 at 3:02:12 AM
On Monday, 16 October 2017 20:28:44 UTC+2, AdWordsApiUser wrote:
>
>
> @Dorian, do you use TSV format by any chance? I keep suspecting that it is
> something to do with TSV format reports, but I am not able to prove it in
> experiments with a hundred or so reports.
>
No, we use CSV reports
We are currently using AdWords reporting, Analytics Reporting API v4 and
Facebook Ads Insights reporting API.
On average AdWords reporting is approximately at least twice as slow as
Analytics Reporting (usually more) and usually three times as slow as
Facebook Ads Insights API. And yes, we have
Some more info:
- Is this across all report types, or is there a specific report type where
you're seeing the slower behavior?
It appears across all report types
- Do you see more rows get returned or anything else changed in the content
of the reports?
No Change
- For a single report, how
I have been running tests the last couple of weeks.
Unfortunately, as I do not have a snapshot of what throughput we used to
get earlier, all I have been trying with is different settings: GZIP,
no-GIP, different download formats (as reported in another thread), but
nothing seems to affect
Hello,
FWIW, we also have experienced somewhat of a performance degradation in the
reporting infrastructure.
We have one job in particular that collects a number of KPIs and structural
data for a few hundred accounts using non-AWQL report definitions, and up
until September 7th its run time
Let me run some tests and gather more data over the weekend to support my
case. I'll update with my findings.
On Wednesday, September 27, 2017 at 6:08:11 PM UTC+5:30, Michael Cloonan
(AdWords API Team) wrote:
>
> Hello,
>
> No changes were made that should affect reporting speed, so I have some
Hello,
No changes were made that should affect reporting speed, so I have some
followup questions to see if we can determine the root cause here.
- Is this across all report types, or is there a specific report type where
you're seeing the slower behavior?
- Do you see more rows get returned
Hello,
No updates yet. I will follow up with the team to see what they've found so
far. I will post here when I have any information to share.
Regards,
Mike, AdWords API Team
On Tuesday, September 26, 2017 at 5:00:47 AM UTC-4, AdWordsApiUser wrote:
>
> Any updates on this? Thanks!
>
> On
Any updates on this? Thanks!
On Thursday, September 21, 2017 at 12:32:37 PM UTC+5:30, AdWordsApiUser
wrote:
>
> I saw this new thread mentioning the slowdown in TSV reports - we use TSV
> reports exclusively - probably that is the issue -
>
I saw this new thread mentioning the slowdown in TSV reports - we use TSV
reports exclusively - probably that is the issue
-
https://groups.google.com/forum/?utm_medium=email_source=footer#!topic/adwords-api/lnuRYUwohNw
A swift resolution will be appreciated :-)
MG
On Tuesday, September 19,
Hello,
No, that will not be necessary; you specifically specified AWQL so I wanted
to know if you had done any tests narrowing that down.
When you say your "job", you mean that your job runs multiple reports that,
in aggregate, used to take 8 hours and now take 16, right? It's not a
single
Hi Michael,
Thanks for your reply. We only use AWQL styled queries, so I don't know right
now if that could be the reason. Do you suggest that we try using the
definition styled reports and compare performance? As I mentioned earlier, my
job that used to get over in 8 hours now takes 16.
Hello,
Are you only seeing this issue with AWQL reports, or are you seeing the
same issue if you run reports with the definition-style selector as well?
I'm curious if it's AWQL-specific or if the slowdown is general to all
reporting.
Regards,
Mike, AdWords API Team
On Monday, September 18,
Hi Shwetha,
I sent you the details in a private message. Does the version of API we use
affect the speed?
Thanks,
MG
On Friday, September 15, 2017 at 1:32:20 AM UTC+8, Shwetha Vastrad (AdWords
API Team) wrote:
>
> Hi,
>
> There isn't an ongoing issue that should be affecting report download
Hi,
There isn't an ongoing that should be affecting report download latency via
AdWords API. Could you provide the report definitions and the
clientCustomerId where you observe the report download latency has
increased? Could you also provide an approximate time when you started
seeing this
Hi,
I am seeing it as well. Can you tell us if there is an actual issue on your
end?
On Monday, September 11, 2017 at 8:35:56 PM UTC+2, Shwetha Vastrad (AdWords
API Team) wrote:
>
> Hi,
>
> Could you provide the report definitions and the clientCustomerId for
> which you observed reduced
Hi,
Could you provide the report definitions and the clientCustomerId for which
you observed reduced throughput for AdWords API report download? Please use
*Reply
privately to author* when responding
Thanks,
Shwetha, AdWords API Team.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Hi Team,
We're noticing a significant slowdown in the throughput of the AWQL
Reporting using the API since last week, where we're spending about 30%-40%
more time than usual. Is this a known issue, or something that is being
changed? Any insights will be appreciated.
Cheers, and have a great
27 matches
Mail list logo
