te')); return $arr; } /* 遍历用户所有主题 * @param $uid 用户ID * @param int $page 页数 * @param int $pagesize 每页记录条数 * @param bool $desc 排序方式 TRUE降序 FALSE升序 * @param string $key 返回的数组用那一列的值作为 key * @param array $col 查询哪些列 */ function thread_tid_find_by_uid($uid, $page = 1, $pagesize = 1000, $desc = TRUE, $key = 'tid', $col = array()) { if (empty($uid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('uid' => $uid), array('tid' => $orderby), $page, $pagesize, $key, $col); return $arr; } // 遍历栏目下tid 支持数组 $fid = array(1,2,3) function thread_tid_find_by_fid($fid, $page = 1, $pagesize = 1000, $desc = TRUE) { if (empty($fid)) return array(); $orderby = TRUE == $desc ? -1 : 1; $arr = thread_tid__find($cond = array('fid' => $fid), array('tid' => $orderby), $page, $pagesize, 'tid', array('tid', 'verify_date')); return $arr; } function thread_tid_delete($tid) { if (empty($tid)) return FALSE; $r = thread_tid__delete(array('tid' => $tid)); return $r; } function thread_tid_count() { $n = thread_tid__count(); return $n; } // 统计用户主题数 大数量下严谨使用非主键统计 function thread_uid_count($uid) { $n = thread_tid__count(array('uid' => $uid)); return $n; } // 统计栏目主题数 大数量下严谨使用非主键统计 function thread_fid_count($fid) { $n = thread_tid__count(array('fid' => $fid)); return $n; } ?>windows - Chrome Slow to Resolve localhost - Stack Overflow

科技改变生活-雨落星辰 - 所有的伟大,都源于一个勇敢的开始

    最新消息：雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客
    你的位置： 首页>programmer>windows - Chrome Slow to Resolve localhost - Stack Overflow

    windows - Chrome Slow to Resolve localhost - Stack Overflow

    programmeradmin3浏览0评论

    My Chrome browser seems to be slow to resolve localhost:3000

    I am in a Windows 10 machine and I SSH into my development laptop via VS Code Remote SSH

    So far here is what I have been able to narrow down.

    • 127.0.0.1:3000 resolution works perfectly fine
    • Firefox localhost:3000 resolution works perfectly fine
    • localhost:3000 on the local laptop that's running the server works fine
    • Added a prefix policy to prefer IPv4 over IPv6 via netsh no effect
    • /etc/hosts has 127.0.0.1 localhost setup
    • If I setup 127.0.0.1 local in /etc/hosts than local:3000 also works fine
    • Going to chrome://net-internals/#dns and checking localhost returns "localhost": ["::1","127.0.0.1"] and seems to ignore the /etc/hosts.

    I feel like this is an IPv6 lookup issue but I can't seem to make Chrome not perform a ::1 lookup for localhost.

    Resolution of localhost vs 127.0.0.1 is almost 10 times slower.

    Open to any suggestions or further debugging recommendations. Thanks in advance!

    Edit: Not sure the reasons for the question downvotes. I can happily revise the question with some direction.

    My Chrome browser seems to be slow to resolve localhost:3000

    I am in a Windows 10 machine and I SSH into my development laptop via VS Code Remote SSH

    So far here is what I have been able to narrow down.

    • 127.0.0.1:3000 resolution works perfectly fine
    • Firefox localhost:3000 resolution works perfectly fine
    • localhost:3000 on the local laptop that's running the server works fine
    • Added a prefix policy to prefer IPv4 over IPv6 via netsh no effect
    • /etc/hosts has 127.0.0.1 localhost setup
    • If I setup 127.0.0.1 local in /etc/hosts than local:3000 also works fine
    • Going to chrome://net-internals/#dns and checking localhost returns "localhost": ["::1","127.0.0.1"] and seems to ignore the /etc/hosts.

    I feel like this is an IPv6 lookup issue but I can't seem to make Chrome not perform a ::1 lookup for localhost.

    Resolution of localhost vs 127.0.0.1 is almost 10 times slower.

    Open to any suggestions or further debugging recommendations. Thanks in advance!

    Edit: Not sure the reasons for the question downvotes. I can happily revise the question with some direction.

    • windows
    • google-chrome
    Share Improve this question edited Feb 18 at 1:59 Dan asked Feb 17 at 21:37 DanDan 2,3132 gold badges21 silver badges43 bronze badges
    Add a comment  | 

    1 Answer 1

    Reset to default 0

    If I remember correctly on Windows the name resolution of localhost to the actual ip address is slow because, when it tries to route to the correct ip there is a cooldown in which it awaits a response. I not sure though.

    Most solutions just suggest that you change to the actual ip address.

    You could try the solutions suggested here, I cannot confirm if it will work for you https://superuser/questions/436574/ipv4-vs-ipv6-priority-in-windows-7/436944#436944

    与本文相关的文章

    发布评论

    评论列表(0)

    1. 暂无评论