Just to let you know - since yesterday the original query started to
perform like before, 3-4 seconds instead of 40-50 seconds during
Wednesday-Thursday.
On Wednesday, January 6, 2016 at 9:59:14 AM UTC+2, di...@easyleads.com
wrote:
>
> Hi,
>
> We encounter a heavy performanc
ts* ran OK up to a couple of days
>>>> ago.*
>>>> Now the same reports seem to be taking too much time so we get an
>>>> exception - com.google.api.ads.adwords.lib.utils.ReportException:
>>>> Problem sending data to report download server
>
api.ads.adwords.lib.utils.ReportException:
>>> Problem sending data to report download server
>>>
>>> Is there currently an issue with the reporting on large accounts causing
>>> the report to fail?
>>>
>>> Thanks.
>>>
>>>
rt to fail?
>>
>> Thanks.
>>
>> On Wednesday, January 6, 2016 at 9:59:14 AM UTC+2, di...@easyleads.com
>> wrote:
>>>
>>> Hi,
>>>
>>> We encounter a heavy performance issue with ACCOUNT_PERFORMANCE_REPORT
>>> on one of o
accounts causing
> the report to fail?
>
> Thanks.
>
> On Wednesday, January 6, 2016 at 9:59:14 AM UTC+2, di...@easyleads.com
> wrote:
>>
>> Hi,
>>
>> We encounter a heavy performance issue with ACCOUNT_PERFORMANCE_REPORT on
>> one of our accounts.
reporting on large accounts causing
the report to fail?
Thanks.
On Wednesday, January 6, 2016 at 9:59:14 AM UTC+2, di...@easyleads.com
wrote:
>
> Hi,
>
> We encounter a heavy performance issue with ACCOUNT_PERFORMANCE_REPORT on
> one of our accounts.
>
> We understand tha
:
>
> Hi,
>
> We encounter a heavy performance issue with ACCOUNT_PERFORMANCE_REPORT on
> one of our accounts.
>
> We understand that the query isn't the simplest in terms of complexity,
> but the response time is reasonable for several hundreds of accounts we
>
Hi,
We encounter a heavy performance issue with ACCOUNT_PERFORMANCE_REPORT on
one of our accounts.
We understand that the query isn't the simplest in terms of complexity, but
the response time is reasonable for several hundreds of accounts we tested.
Query 1 (last year): SELECT D
