site speed and content translation

[Aaron Markham <aa...@gmail.com>]

Hi MXNet community!

I recently looked through stats for Q1 and compared them to previous
quarters. I also checked out some of the insights. Here's what I found:

MXNet traffic was relatively flat with a 0.24% gain in users QoQ, but a
slight decline of users of -2.36% month over month. However, there was a
noticeable decline in traffic from Asian language users, in particular
Chinese (-17%), Japanese (-7%), Korean (-18%), and Taiwanese (-19%),
meanwhile English was up around 10%.

Google’s insights mention that the website loads much slower in China than
everywhere else with an average of 19 seconds. This will frustrate many
customers and it would be worth investigating CDN options for the website.
This is all the more important because *China is the number one country
using the MXNet website*.

So I have two suggestions:

1. Localize the site for Chinese customers
2. Get some CDN or better mirror for Chinese customers so page load time
isn't so horrible

For (1), I was involved a long while back on a loc project for MXNet, but
that sputtered out for reasons not worth getting into, but suffice to say,
it can be a bit complicated. Scoping out what to translate is key. My
suggestion is to translate just the main site, the Python guides, html
versions of notebooks, but not the API reference, and not any other
language APIs.

For (2), IDK. Ask Apache Infra about it? AWS is bound to have an option
here too.

Cheers,
Aaron

Re: site speed and content translation

[sandeep krishnamurthy <sa...@gmail.com>]

Thank you Aaron and Foivos for bringing this up.

Any other concerns in the MXNet website that we need to tackle?

Best,
Sandeep

On Mon, 27 Apr 2020, 11:17 am Aaron Markham, <aa...@gmail.com>
wrote:

> I created a ticked with Apache Infra. Searching Jira reveals that there has
> been an experimental CDN in China for some time now.
> https://issues.apache.org/jira/browse/INFRA-20203
> Foivos, thanks for the info. I mention the issue in the ticket too. Let's
> see what they say about CDN support for China and Australia.
>
> Cheers,
> Aaron
>
> On Fri, Apr 24, 2020 at 9:17 AM Foivos Diakogiannis <
> phoevos.diakogiannis@gmail.com> wrote:
>
> > Dear all,
> >
> > the loading speed from Australia (Perth at least) is also bad. I avoid
> > visiting the site for documentation for this reason.
> >
> > Thank you all for this amazing tool that you've built and maintain.
> >
> > Kind regards,
> > Foivos
> >
> > On Sat, Apr 25, 2020 at 12:05 AM Aaron Markham <
> aaron.s.markham@gmail.com>
> > wrote:
> >
> > > Hi MXNet community!
> > >
> > > I recently looked through stats for Q1 and compared them to previous
> > > quarters. I also checked out some of the insights. Here's what I found:
> > >
> > > MXNet traffic was relatively flat with a 0.24% gain in users QoQ, but a
> > > slight decline of users of -2.36% month over month. However, there was
> a
> > > noticeable decline in traffic from Asian language users, in particular
> > > Chinese (-17%), Japanese (-7%), Korean (-18%), and Taiwanese (-19%),
> > > meanwhile English was up around 10%.
> > >
> > > Google’s insights mention that the website loads much slower in China
> > than
> > > everywhere else with an average of 19 seconds. This will frustrate many
> > > customers and it would be worth investigating CDN options for the
> > website.
> > > This is all the more important because *China is the number one country
> > > using the MXNet website*.
> > >
> > > So I have two suggestions:
> > >
> > > 1. Localize the site for Chinese customers
> > > 2. Get some CDN or better mirror for Chinese customers so page load
> time
> > > isn't so horrible
> > >
> > > For (1), I was involved a long while back on a loc project for MXNet,
> but
> > > that sputtered out for reasons not worth getting into, but suffice to
> > say,
> > > it can be a bit complicated. Scoping out what to translate is key. My
> > > suggestion is to translate just the main site, the Python guides, html
> > > versions of notebooks, but not the API reference, and not any other
> > > language APIs.
> > >
> > > For (2), IDK. Ask Apache Infra about it? AWS is bound to have an option
> > > here too.
> > >
> > > Cheers,
> > > Aaron
> > >
> >
>

Re: site speed and content translation

[Aaron Markham <aa...@gmail.com>]

I created a ticked with Apache Infra. Searching Jira reveals that there has
been an experimental CDN in China for some time now.
https://issues.apache.org/jira/browse/INFRA-20203
Foivos, thanks for the info. I mention the issue in the ticket too. Let's
see what they say about CDN support for China and Australia.

Cheers,
Aaron

On Fri, Apr 24, 2020 at 9:17 AM Foivos Diakogiannis <
phoevos.diakogiannis@gmail.com> wrote:

> Dear all,
>
> the loading speed from Australia (Perth at least) is also bad. I avoid
> visiting the site for documentation for this reason.
>
> Thank you all for this amazing tool that you've built and maintain.
>
> Kind regards,
> Foivos
>
> On Sat, Apr 25, 2020 at 12:05 AM Aaron Markham <aa...@gmail.com>
> wrote:
>
> > Hi MXNet community!
> >
> > I recently looked through stats for Q1 and compared them to previous
> > quarters. I also checked out some of the insights. Here's what I found:
> >
> > MXNet traffic was relatively flat with a 0.24% gain in users QoQ, but a
> > slight decline of users of -2.36% month over month. However, there was a
> > noticeable decline in traffic from Asian language users, in particular
> > Chinese (-17%), Japanese (-7%), Korean (-18%), and Taiwanese (-19%),
> > meanwhile English was up around 10%.
> >
> > Google’s insights mention that the website loads much slower in China
> than
> > everywhere else with an average of 19 seconds. This will frustrate many
> > customers and it would be worth investigating CDN options for the
> website.
> > This is all the more important because *China is the number one country
> > using the MXNet website*.
> >
> > So I have two suggestions:
> >
> > 1. Localize the site for Chinese customers
> > 2. Get some CDN or better mirror for Chinese customers so page load time
> > isn't so horrible
> >
> > For (1), I was involved a long while back on a loc project for MXNet, but
> > that sputtered out for reasons not worth getting into, but suffice to
> say,
> > it can be a bit complicated. Scoping out what to translate is key. My
> > suggestion is to translate just the main site, the Python guides, html
> > versions of notebooks, but not the API reference, and not any other
> > language APIs.
> >
> > For (2), IDK. Ask Apache Infra about it? AWS is bound to have an option
> > here too.
> >
> > Cheers,
> > Aaron
> >
>

Re: site speed and content translation

[Foivos Diakogiannis <ph...@gmail.com>]

Dear all,

the loading speed from Australia (Perth at least) is also bad. I avoid
visiting the site for documentation for this reason.

Thank you all for this amazing tool that you've built and maintain.

Kind regards,
Foivos

On Sat, Apr 25, 2020 at 12:05 AM Aaron Markham <aa...@gmail.com>
wrote:

> Hi MXNet community!
>
> I recently looked through stats for Q1 and compared them to previous
> quarters. I also checked out some of the insights. Here's what I found:
>
> MXNet traffic was relatively flat with a 0.24% gain in users QoQ, but a
> slight decline of users of -2.36% month over month. However, there was a
> noticeable decline in traffic from Asian language users, in particular
> Chinese (-17%), Japanese (-7%), Korean (-18%), and Taiwanese (-19%),
> meanwhile English was up around 10%.
>
> Google’s insights mention that the website loads much slower in China than
> everywhere else with an average of 19 seconds. This will frustrate many
> customers and it would be worth investigating CDN options for the website.
> This is all the more important because *China is the number one country
> using the MXNet website*.
>
> So I have two suggestions:
>
> 1. Localize the site for Chinese customers
> 2. Get some CDN or better mirror for Chinese customers so page load time
> isn't so horrible
>
> For (1), I was involved a long while back on a loc project for MXNet, but
> that sputtered out for reasons not worth getting into, but suffice to say,
> it can be a bit complicated. Scoping out what to translate is key. My
> suggestion is to translate just the main site, the Python guides, html
> versions of notebooks, but not the API reference, and not any other
> language APIs.
>
> For (2), IDK. Ask Apache Infra about it? AWS is bound to have an option
> here too.
>
> Cheers,
> Aaron
>