mongo db poor performance while doing text serch with number.











up vote
1
down vote

favorite












I have a collection called "torrents" with about 3.2M Documents. which basicly contains public torrent metadata.



Schema:



let mongoose = require('mongoose');

let TorrentSchema = mongoose.Schema({
infohash: {type: String, index: true, unique: true},
title: {type: String, index: true},
category: {type: String, default: "Unknown", index: true},
size: {type: Number, default: 0},
trackers: [{
downloads: {type: Number},
peers: {type: Number},
seeds: {type: Number},
tracker: {type: String}
}],
files: [{path: String, length: Number}],
swarm: {
seeders: {type: Number, default: 0, index: -1},
leechers: {type: Number, default: 0}
},
imported: {type: Date, default: Date.now, index: true},
lastmod: {type: Date, default: Date.now, index: true}
});

TorrentSchema.virtual('getFiles').set(function () {
return this.map(res => {
if (typeof res === "string") return [{path: res, length: 0}];
return res;
})
});

TorrentSchema.virtual('downloads').get(function () {
let downloads = 0;
for (let download of this.trackers) {
downloads += download.downloads
}
return downloads;
});

TorrentSchema.index({title: 'text'}, { language_override: 'none' });
module.exports = mongoose.model('Torrent', TorrentSchema);


Now that the problem is when I am doing a text search with a keyword which also contents number(s) the search query taking a long time to execute.



  let q = req.query.q;
q = q.split(/[s]/).filter(n => n).map( str => `"${str}"`).join(" ");
let PERPAGE = 20;
let query = {$text: {$search: q}};
// Tottent Is the same schema as above.
let search = await Torrent.find(query).sort({"swarm.seeders" : -1}).select("-files").limit(PERPAGE).skip(skip);


now the issue is. when searching with letters like "ubuntu" it going really fast. but the problem arises when searching with a string which also contains numbers. Like "ubuntu 18", strings with no numbers like "ubuntu iso" taking nowhere near the time. the same thing happening when searching some other keywords like "somevideo 1080p", "somemovie 2" etc.



guys do you have any fix for this issue?










share|improve this question


























    up vote
    1
    down vote

    favorite












    I have a collection called "torrents" with about 3.2M Documents. which basicly contains public torrent metadata.



    Schema:



    let mongoose = require('mongoose');

    let TorrentSchema = mongoose.Schema({
    infohash: {type: String, index: true, unique: true},
    title: {type: String, index: true},
    category: {type: String, default: "Unknown", index: true},
    size: {type: Number, default: 0},
    trackers: [{
    downloads: {type: Number},
    peers: {type: Number},
    seeds: {type: Number},
    tracker: {type: String}
    }],
    files: [{path: String, length: Number}],
    swarm: {
    seeders: {type: Number, default: 0, index: -1},
    leechers: {type: Number, default: 0}
    },
    imported: {type: Date, default: Date.now, index: true},
    lastmod: {type: Date, default: Date.now, index: true}
    });

    TorrentSchema.virtual('getFiles').set(function () {
    return this.map(res => {
    if (typeof res === "string") return [{path: res, length: 0}];
    return res;
    })
    });

    TorrentSchema.virtual('downloads').get(function () {
    let downloads = 0;
    for (let download of this.trackers) {
    downloads += download.downloads
    }
    return downloads;
    });

    TorrentSchema.index({title: 'text'}, { language_override: 'none' });
    module.exports = mongoose.model('Torrent', TorrentSchema);


    Now that the problem is when I am doing a text search with a keyword which also contents number(s) the search query taking a long time to execute.



      let q = req.query.q;
    q = q.split(/[s]/).filter(n => n).map( str => `"${str}"`).join(" ");
    let PERPAGE = 20;
    let query = {$text: {$search: q}};
    // Tottent Is the same schema as above.
    let search = await Torrent.find(query).sort({"swarm.seeders" : -1}).select("-files").limit(PERPAGE).skip(skip);


    now the issue is. when searching with letters like "ubuntu" it going really fast. but the problem arises when searching with a string which also contains numbers. Like "ubuntu 18", strings with no numbers like "ubuntu iso" taking nowhere near the time. the same thing happening when searching some other keywords like "somevideo 1080p", "somemovie 2" etc.



    guys do you have any fix for this issue?










    share|improve this question
























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I have a collection called "torrents" with about 3.2M Documents. which basicly contains public torrent metadata.



      Schema:



      let mongoose = require('mongoose');

      let TorrentSchema = mongoose.Schema({
      infohash: {type: String, index: true, unique: true},
      title: {type: String, index: true},
      category: {type: String, default: "Unknown", index: true},
      size: {type: Number, default: 0},
      trackers: [{
      downloads: {type: Number},
      peers: {type: Number},
      seeds: {type: Number},
      tracker: {type: String}
      }],
      files: [{path: String, length: Number}],
      swarm: {
      seeders: {type: Number, default: 0, index: -1},
      leechers: {type: Number, default: 0}
      },
      imported: {type: Date, default: Date.now, index: true},
      lastmod: {type: Date, default: Date.now, index: true}
      });

      TorrentSchema.virtual('getFiles').set(function () {
      return this.map(res => {
      if (typeof res === "string") return [{path: res, length: 0}];
      return res;
      })
      });

      TorrentSchema.virtual('downloads').get(function () {
      let downloads = 0;
      for (let download of this.trackers) {
      downloads += download.downloads
      }
      return downloads;
      });

      TorrentSchema.index({title: 'text'}, { language_override: 'none' });
      module.exports = mongoose.model('Torrent', TorrentSchema);


      Now that the problem is when I am doing a text search with a keyword which also contents number(s) the search query taking a long time to execute.



        let q = req.query.q;
      q = q.split(/[s]/).filter(n => n).map( str => `"${str}"`).join(" ");
      let PERPAGE = 20;
      let query = {$text: {$search: q}};
      // Tottent Is the same schema as above.
      let search = await Torrent.find(query).sort({"swarm.seeders" : -1}).select("-files").limit(PERPAGE).skip(skip);


      now the issue is. when searching with letters like "ubuntu" it going really fast. but the problem arises when searching with a string which also contains numbers. Like "ubuntu 18", strings with no numbers like "ubuntu iso" taking nowhere near the time. the same thing happening when searching some other keywords like "somevideo 1080p", "somemovie 2" etc.



      guys do you have any fix for this issue?










      share|improve this question













      I have a collection called "torrents" with about 3.2M Documents. which basicly contains public torrent metadata.



      Schema:



      let mongoose = require('mongoose');

      let TorrentSchema = mongoose.Schema({
      infohash: {type: String, index: true, unique: true},
      title: {type: String, index: true},
      category: {type: String, default: "Unknown", index: true},
      size: {type: Number, default: 0},
      trackers: [{
      downloads: {type: Number},
      peers: {type: Number},
      seeds: {type: Number},
      tracker: {type: String}
      }],
      files: [{path: String, length: Number}],
      swarm: {
      seeders: {type: Number, default: 0, index: -1},
      leechers: {type: Number, default: 0}
      },
      imported: {type: Date, default: Date.now, index: true},
      lastmod: {type: Date, default: Date.now, index: true}
      });

      TorrentSchema.virtual('getFiles').set(function () {
      return this.map(res => {
      if (typeof res === "string") return [{path: res, length: 0}];
      return res;
      })
      });

      TorrentSchema.virtual('downloads').get(function () {
      let downloads = 0;
      for (let download of this.trackers) {
      downloads += download.downloads
      }
      return downloads;
      });

      TorrentSchema.index({title: 'text'}, { language_override: 'none' });
      module.exports = mongoose.model('Torrent', TorrentSchema);


      Now that the problem is when I am doing a text search with a keyword which also contents number(s) the search query taking a long time to execute.



        let q = req.query.q;
      q = q.split(/[s]/).filter(n => n).map( str => `"${str}"`).join(" ");
      let PERPAGE = 20;
      let query = {$text: {$search: q}};
      // Tottent Is the same schema as above.
      let search = await Torrent.find(query).sort({"swarm.seeders" : -1}).select("-files").limit(PERPAGE).skip(skip);


      now the issue is. when searching with letters like "ubuntu" it going really fast. but the problem arises when searching with a string which also contains numbers. Like "ubuntu 18", strings with no numbers like "ubuntu iso" taking nowhere near the time. the same thing happening when searching some other keywords like "somevideo 1080p", "somemovie 2" etc.



      guys do you have any fix for this issue?







      node.js mongodb mongoose






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 10 at 19:17









      Bubun

      397




      397
























          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote













          It seems, after querying with same keyword couple of times, the query speed seems increased significantly.






          share|improve this answer





















            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














             

            draft saved


            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53242545%2fmongo-db-poor-performance-while-doing-text-serch-with-number%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            It seems, after querying with same keyword couple of times, the query speed seems increased significantly.






            share|improve this answer

























              up vote
              0
              down vote













              It seems, after querying with same keyword couple of times, the query speed seems increased significantly.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                It seems, after querying with same keyword couple of times, the query speed seems increased significantly.






                share|improve this answer












                It seems, after querying with same keyword couple of times, the query speed seems increased significantly.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 11 at 15:44









                Bubun

                397




                397






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53242545%2fmongo-db-poor-performance-while-doing-text-serch-with-number%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Xamarin.iOS Cant Deploy on Iphone

                    Glorious Revolution

                    Dulmage-Mendelsohn matrix decomposition in Python