Announcement

Collapse
No announcement yet.

Sharing to facebook is very slow

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Sharing to facebook is very slow

    It takes 20+ seconds to share a post to 1 facebook page and 1 facebook group with the blog2social plugin.

    Is there anyway to speed up this?

    Thank you!

  • #2
    Hello Ying,

    Thank you so much for reaching out. First of all, please ensure that your web server's performance is sufficient enough to host and enable a proper functioning of your WordPress installation and thus, Blog2Social.

    Please check if your blog meets the system requirements as shown here: https://www.blog2social.com/en/faq/i...147&artlang=en

    This delay is is usually the result of a slow server with an overload or lack of server capacity.

    If your website is hosted on a server with low server capacity, you can turn on the Blog2Social Legacy Mode to reduce server load. In Legacy Mode, the plugin will load contents one after the other (asynchronous loading) instead of loading all at once. Some web hosting services also limit the number of outgoing connections. In this case, the Legacy Mode makes sure that connections to your social media accounts are loaded successively.

    To activate Legacy Mode you can go to “Blog2Social -> Settings -> General -> System” and tick the box saying “activate Legacy Mode”.


    Please let me know if this solution works for you.


    Best regards

    Alexander

    Comment


    • #3
      Hi Alexander,

      Thank you for the reply!

      The server capacity shouldn't be a problem. I'm using a 8 vCPU / 16G dedicated CPU linode vm. The current workload of the website is pretty low.

      I found there is a plugin warning. I'm not sure if it has any performance impact. How can I fix this conflict?

      Click image for larger version

Name:	Capture.PNG
Views:	30
Size:	89.7 KB
ID:	272

      Comment


      • #4
        Hello Ying,

        Thank you for your reply.

        The process of sending out a post to multiple social networks does take some time for the system to prepare everything so it can be sent to the specific networks. This delay is depending on the amount of your network selection in your networks collection.

        Could you be so kind tell me, did you try to enable the mentioned legacy mode? Even if a server is fast, simultaneous outgoing connections are sometimes limited. In this case enabling the legacy mode to load them asynchronously might speed the process up quite a bit. Please try this and let me know if this works for you.

        In regard to the plugin warning:

        It is possible that “All in One WP Security” is also interfering with the connection to the Blog2Social servers. Resolving the open conflict by disabling the specific plugin could help make sure that Blog2Social can work flawless again.

        I am looking forward to your reply.

        Best regards

        Alexander

        Comment


        • #5
          I have disabled "all in one WP security" and enabled legacy mode. But there is no effect to the sharing speed.

          I only share to facebook page and facebook group, no other social network.

          Comment


          • #6
            It takes about 11 seconds to share to facebook group only.
            Sharing to both facebook page and group takes 20+ seconds

            Is there any way to find out how much time is spent on each step? (for example, how much time is spent on sending the image to facebook?)

            Is there a debug log / trace log in blog2social?

            Comment


            • #7
              Hello Ying,

              Thank you so much for reaching out again.

              We will check this for you and get back to you as soon as we have new information.

              Best regards

              Alexander

              Comment


              • #8
                Thank you!

                Comment


                • #9
                  Hello Ying,

                  Thank you for your patience. I have checked your request carefully. The amount of time that is required to process a task in Blog2Social is in a regular time-frame on your site. Please contact your hosting provider to be able to speed this up. Please ask them why the request on your server has to wait until is is processed. The delay is probably happening because your server needs some time until the request is sent to us.

                  Please let me know if you have any other question about Blog2Social.

                  Best regards

                  Alexander

                  Comment


                  • #10
                    Hi Alexander,

                    Thank you for the reply!

                    I have tested sharing posts to facebook from an AWS EC2 instance (us-west-1 region). It takes about 23 seconds to share a post to both facebook group. This is about the same as sharing from the Linode instance (north California region).

                    We are operating our own linux / apache / php host. There is no such a "hosting provider".

                    I have tested two different cloud providers (Amazon AWS and Linode). Two different software configurations. The result is the same.

                    The Linode host configuration:
                    8 vCPU cores, 16GB memory
                    CentOS 7
                    Apache 2.4.43
                    Php 7.3.18
                    MySQL DB


                    The AWS EC2 host configuration:
                    4 vCPU cores, 16GB memory
                    Debian 10
                    Apache 2.4.38
                    Php-fpm 7.3.14
                    Amazon Aurora DB

                    The linode host has moderate web traffic. The aws host is our development server, which has no public traffic.

                    Comment


                    • #11
                      I made a tcpdump on my development host in AWS:

                      22:04:46.178939 IP 10.0.1.21.56589 > 10.0.0.2.53: 59502+ A? developer.blog2social.com. (43)
                      22:04:46.178945 IP 10.0.1.21.56589 > 10.0.0.2.53: 32372+ AAAA? developer.blog2social.com. (43)
                      22:04:46.179106 IP 10.0.0.2.53 > 10.0.1.21.56589: 59502 1/0/0 A 178.77.85.168 (59)
                      22:04:46.179145 IP 10.0.0.2.53 > 10.0.1.21.56589: 32372 1/0/0 AAAA 2a01:488:42:1000:b24d:55a8:ffb8:ccaf (71)
                      22:04:46.179290 IP 10.0.1.21.42018 > 178.77.85.168.443: Flags [S], seq 202089124, win 62727, options [mss 8961,sackOK,TS val 631992675 ecr 0,nop,wscale 7], length 0
                      22:04:46.338496 IP 178.77.85.168.443 > 10.0.1.21.42018: Flags [S.], seq 1726705905, ack 202089125, win 28960, options [mss 1460,sackOK,TS val 1922277874 ecr 631992675,nop,wscale 5], length 0
                      22:04:46.338522 IP 10.0.1.21.42018 > 178.77.85.168.443: Flags [.], ack 1, win 491, options [nop,nop,TS val 631992834 ecr 1922277874], length 0
                      22:04:46.346948 IP 10.0.1.21.42018 > 178.77.85.168.443: Flags [P.], seq 1:518, ack 1, win 491, options [nop,nop,TS val 631992842 ecr 1922277874], length 517
                      22:04:46.506167 IP 178.77.85.168.443 > 10.0.1.21.42018: Flags [.], ack 518, win 939, options [nop,nop,TS val 1922278041 ecr 631992842], length 0
                      22:04:46.529347 IP 178.77.85.168.443 > 10.0.1.21.42018: Flags [P.], seq 1:4150, ack 518, win 939, options [nop,nop,TS val 1922278065 ecr 631992842], length 4149
                      22:04:46.529368 IP 10.0.1.21.42018 > 178.77.85.168.443: Flags [.], ack 4150, win 459, options [nop,nop,TS val 631993025 ecr 1922278065], length 0
                      22:04:46.530489 IP 10.0.1.21.42018 > 178.77.85.168.443: Flags [P.], seq 518:709, ack 4150, win 459, options [nop,nop,TS val 631993026 ecr 1922278065], length 191
                      22:04:46.690518 IP 178.77.85.168.443 > 10.0.1.21.42018: Flags [P.], seq 4150:4201, ack 709, win 972, options [nop,nop,TS val 1922278226 ecr 631993026], length 51
                      22:04:46.690663 IP 10.0.1.21.42018 > 178.77.85.168.443: Flags [P.], seq 709:1068, ack 4201, win 459, options [nop,nop,TS val 631993186 ecr 1922278226], length 359
                      22:04:46.853021 IP 178.77.85.168.443 > 10.0.1.21.42018: Flags [P.], seq 4201:4255, ack 1068, win 1006, options [nop,nop,TS val 1922278388 ecr 631993186], length 54
                      22:04:46.853118 IP 10.0.1.21.42018 > 178.77.85.168.443: Flags [.], seq 1068:2516, ack 4255, win 459, options [nop,nop,TS val 631993349 ecr 1922278388], length 1448
                      22:04:46.853122 IP 10.0.1.21.42018 > 178.77.85.168.443: Flags [.], seq 2516:3964, ack 4255, win 459, options [nop,nop,TS val 631993349 ecr 1922278388], length 1448
                      22:04:46.853126 IP 10.0.1.21.42018 > 178.77.85.168.443: Flags [.], seq 3964:5412, ack 4255, win 459, options [nop,nop,TS val 631993349 ecr 1922278388], length 1448
                      22:04:46.853129 IP 10.0.1.21.42018 > 178.77.85.168.443: Flags [P.], seq 5412:5756, ack 4255, win 459, options [nop,nop,TS val 631993349 ecr 1922278388], length 344
                      22:04:47.012390 IP 178.77.85.168.443 > 10.0.1.21.42018: Flags [.], ack 5756, win 1299, options [nop,nop,TS val 1922278548 ecr 631993349], length 0
                      22:05:03.939616 IP 178.77.85.168.443 > 10.0.1.21.42018: Flags [P.], seq 4255:5007, ack 5756, win 1299, options [nop,nop,TS val 1922295475 ecr 631993349], length 752
                      22:05:03.939643 IP 178.77.85.168.443 > 10.0.1.21.42018: Flags [F.], seq 5007, ack 5756, win 1299, options [nop,nop,TS val 1922295475 ecr 631993349], length 0
                      22:05:03.939956 IP 10.0.1.21.42018 > 178.77.85.168.443: Flags [P.], seq 5756:5787, ack 5008, win 454, options [nop,nop,TS val 632010436 ecr 1922295475], length 31
                      22:05:03.940764 IP 10.0.1.21.42018 > 178.77.85.168.443: Flags [F.], seq 5787, ack 5008, win 454, options [nop,nop,TS val 632010437 ecr 1922295475], length 0




                      At the 3 red lines, you can see that
                      1) my host made a https request to blog2social's host (developer.blog2social.com / 178.77.85.168) at 22:04:46.853129
                      2) after 0.16 sec, my host received the ack, which means the blog2social host has received the request
                      3) it took about 17 seconds for the blog2social host to response the request at 22:05:03.939616

                      I think it's very clear that, the time was spent on the developer.blog2social.com server in Host Europe cloud. It has nothing to do with my server nor my cloud provider.

                      I think the other log2social users (at least those in the US) are also suffering from this performance issue.
                      Could you please ask your engineers to check the log of developer.blog2social.com to find out why it took so long to share the posts?

                      Please feel free to let me know if you need any other information to help you debug this issue

                      Thank you very much!
                      Ying

                      Comment


                      • #12
                        Hello Ying,

                        our provider says that he can't reproduced it that way.
                        To be able to reproduce it, he would like to have information about how you tested, with which software and which parameters you used?
                        The precide the better
                        Best
                        Andreas

                        Comment


                        • #13
                          The software I used: blog2social version 6.4.1 with Pro license
                          How to test it: create a post on wordpress, with a featured image, click "Customize & Schedule Social Media Posts", then click share

                          Comment


                          • #14
                            If you can't help us to solve this performance issue, I will have to ask for a full refund of the $139 I paid for the Pro license

                            Comment


                            • #15
                              Hello Ying,
                              slow connection could also have something to do with the individual configuration. Could you give us temporary access to your blog to proof that? You could send me a PN.
                              Cheers,
                              Andreas

                              Comment

                              Working...
                              X